| Age | Commit message (Collapse) | Author |
|---|
|
|
|
A cursor is a mark, if the text containing the mark is removed the
cursor is lost. In this case we try to fall back to the previously
known cursor position/mark. This should improve undo operations
for filter commands.
|
|
As a consequence the general cursor placement code takes effect and
always places the cursor in the middle of the window when moving out
of the viewable range.
Whether this behavior is desirable remains to be seen.
|
|
|
|
This changes which viewport is being displayed after the primary
cursor moves out of the currently viewable area.
Close #164, #274, #278
|
|
Close #216
|
|
This should fix inconsistency in the Lua API.
|
|
Can be used to specify the number of bytes before the visible area
to consider for syntax highlighting.
Defaults to 32K for now, whereas before it was 16K.
|
|
|
|
|
|
|
|
To create a cursor even if there already exists one at the same
position. Should only be used if all but one of the cursors will
later be removed.
|
|
If there exist multiple cursors, [n/m] is added to the status bar.
Meaning the n-th cursor out of the existing m cursors is currently
the primary one.
|
|
Do not crash if for some reason view->{start,end} have outdated values.
|
|
indicating whether cursor could be removed
|
|
|
|
We place the end mark inside the selection as opposted to on the character
immediately following it. This is better when selections are touching each
other. Previously for two seletions [a][b] the end mark for selection
a would be at the same location as the start mark of selection b. Thus
when for example the content of selection b is deleted it would also
destroy selection a, because the end mark would no longer be valid.
|
|
|
|
Fail if there is already a cursor located at the requested position.
|
|
The number of columns i.e. maximal number of cursors located on the
same line can be obtained by view_cursors_column_count.
Column addressing is zero based, valid indexes are [0, max-1].
Assuming there is a cursor on every letter:
a
b c
d e f
g h
i
max column would be 3, and the following would iterate over the
cursors forming the second column [c, e, h]:
for (Cursor *c = view_cursors_column(view, 1); c; c = view_cursors_column_next(c, 1))
...
|
|
This is currently only enforced upon creation i.e. we assume
that after creation a cursor can not change its relative ordering
with respect to its neighbors.
The existing code assumes that when iterating through cursors with:
for (Cursor *c = view_cursors(view); c; c = view_cursors_next(c))
...
new cursors created with view_cursors_new do not show up.
This assumption is preserved under the following conditions:
* it only holds for the most recent view_cursors call
As a consequence when doing nested iterations new cursors
will be yielded once the inner view_cursors call was performed.
* view_cursors_primary_get is not called
|
|
|
|
|
|
|
|
|
|
This for example affects the default background color and cursor
related settings.
|
|
|
|
|
|
The currently visible display port is always adjusted
in a way that the primary cursor is visible.
|
|
|
|
|
|
Allow colorcolumn to be greater than the view width.
Lines that wrap now have the colorcolumn highlighted.
|
|
That is from now on use vis:method instead of vis.method
|
|
|
|
|
|
This allows them to be placed into the read only ELF section.
|
|
Disable absolute line numbers for large files (currently
anything bigger than 32MiB). This speeds up moving around
with for example nn% since no new lines need to be calculated.
Of course movements like :nn will be unaffected.
The optimizations can be disabled by explicitly enabling
absolute line numbers as in :set number
|
|
|
|
Close #148
|
|
It returns the range covered by the selection of the primary cursor.
|
|
This reverts 2f4b69cc67e8863e5789817ed5097158e6163621. There are
likely still some problems left when editing the end of a file
at end of the visual area.
|
|
Holding down <Backspace> at the end of the file should not
keep the cursor on the middle line of the window.
|
|
The last new line is added to the cell matrix but failure
is reported to indicate that there is no space left for
further characters.
|
|
This for example now correctly displays tab characters at
the very start of the visible area.
|
|
Lua support can now be disabled at compile time using:
$ make CONFIG_LUA=0
This commit also adds an initial Lua API and provides a few
default hooks.
We now also require Lua >= 5.2 due to the uservalue constructs.
In principle the same functionality could be implemented using
function environments from Lua 5.1.
|
|
The only used event handler was used to update the '< and '>
marks which is now taken care of by the leave handler of the
visual modes.
|
|
|
|
|
|
|
|
They now belong to the cell holding the corresponding regular
(i.e. non-combining) character. This also means that at least
in theory a cell could hold arbitrary amounts of data, in
practice it is limited to 16 bytes.
|
