| Age | Commit message (Collapse) | Author |
|---|
|
These should ideally be paired with setting the capability on
initialize, but for now, the parsing support is there at least for
LSP servers that ignore it (like pylsp).
|
|
The previous fix for that did not take multiple files into account.
|
|
I.e. when you save, it is probably time to remove the completion.
|
|
When in the buflist, you can now press 'S' to save all unsaved
buffers.
|
|
To not collide with the <stdio.h> globals for stdin, stdout and stderr.
|
|
Diagnostic highlight now sets the fg to white and the background to
the appropriate color for the diagnostic severity. Before, we
could end up with a yellow color for warning as background and
a yellow as foreground for a function, which caused unreadable text.
Also fix some more cases where re-render is needed.
|
|
Running a lot faster just causes tearing.
|
|
This is an old xterm feature that most terminals seem to implement.
|
|
|
|
Also make it a bit more robust if we run out of slots.
|
|
Then do not display anything and warn user with a message that
no help was available.
|
|
|
|
It now detects and saves properly.
|
|
We were spawning too many completion requests as part of
the text being changed.
|
|
- It now colors correctly
- Supports searching for unicode symbols
- Make search able to continue when more letters are entered
|
|
Add to buffer_view when jumping to a location.
|
|
Scrolling vertically now keeps two lines of context and overflowing
vertically places dot in middle of screen.
|
|
It now uses the common approach of saving to a different file and
then using rename to the desired filename after the file has been
fully written, thus not corrupting the file in case of a crash
when writing the file.
|
|
|
|
This makes the LSP support complete for now:
- Completion
- Diagnostics
- Goto implementation/declaration
- Rename
- Documentation
- Find references
|
|
- Some unused variables
- Fix zero window size under lldb
- Make instantiation of languages more robust
|
|
Was caused by using a vector that used realloc to grow. That only works
sometimes. Now instead, the buffer list is a chunked linked list, i.e. a
linked list where each element is a fixed size array.
|
|
|
|
|
|
Id did not use position 0 properly and caused it
to "lose" copy/paste information when the kill ring wrapped around.
|
|
Highlight the regular search matches using a
oneshot approach.
|
|
Previously, the code assumed 4.
|
|
Was not doing the correct thing when multiple lines
was added.
|
|
|
|
Previously assumed that column was 0 if more than one line was
inserted. This was never correct.
|
|
|
|
In this case, the end of the buffer is on the last line, however
if there are no lines in the buffer, it would cause an underflow.
|
|
|
|
|
|
Outside the Nix setup, it will be the responsibility of something else
(might be a script) to provide the treesitter grammars.
|
|
This contains the start of an LSP client.
Nothing (except starting the LSP server) works
at the moment and the feature is disabled by default.
|
|
It now instead iterates the actual unicode code points. This is better
than what it was previously doing but it is still not entirely correct
w.r.t to unicode sequences.
This handling of unicode code points does however make it slightly
easier to handle UTF-16 if needed in the future.
This also adds some long needed tests for buffer methods.
|
|
The minibuffer code for handling going back to previous window
after abort was a bit too greedy.
|
|
|
|
|
|
Previously it tried to reload the buffer even though it could not
be watched.
|
|
This is safer since the event is only emitted once the file is closed,
not every time it is modified and it seems to yield more reliable
results.
|
|
Fix the buffer list return key action when buffers have the same name.
Previously, it would pick the first it could find in the buffer list
with the correct buffer name instead of the selected one. Now it uses
text properties to pass the actual buffer pointer along instead.
This however exposed a problem with the clearing of properties and where
in the frame it happens. Search and replace highlighting assumed that
they could color things in their respective command executions. However,
ideally coloring should happen in update functions so now both search
and replace implement the coloring in update hooks for the buffer
they are operating on. For replace, this was already kinda how it
worked and could be adapted with minimal effort. Search on the other
hand needed a bit more rework.
|
|
The crash happened when a new file was opened followed by another
completion. The reason was that not accepting any of the completion
suggestions caused the completion to stay active, causing the context
to not be updated for the next completion.
|
|
|
|
|
|
|
|
|
|
Also make targets dependent on config.mk so that the program
is rebuilt when config.mk changes.
|
|
|
