| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Fix #372
|
|
|
|
|
|
Fix #448
|
|
The vis_keys_feed function is currently unaffected by this change.
It still creates individual undo points. While this is probably
undesirable from an API point of view, it keeps the lua based tests
that use undo points working.
|
|
Previously if you had a mapping for both `a` and `ab` the latter would
in effect be unreachable because the greedy search would always match
and then execute the former. With the new behavior we keep reading keys
until we have a non ambigious sequence. That is after pressing `a` nothing
will happen, if the next key is a `b` we will execute the `ab` mapping
otherwise we will perform `a` and whatever the action is for the next key.
Close #386
|
|
Tests whether the given prefix can be extended to exactly one map element
i.e. true iff the prefix map contains exactly one element.
|
|
Fix #461
|
|
Fix #464
|
|
|
|
|
|
Signed-off-by: Christian Hesse <mail@eworm.de>
|
|
Define EXECUTABLES and install in a loop. Also fix uninstalling
man pages.
|
|
These are called from vis only. So include them in the archive and set PATH
to make vis find them.
|
|
|
|
Previously repeatedly pressing <Ctrl-j> at the start of the file
would keep creating cursors.
|
|
Close #458
|
|
Fix #459
|
|
When encountering a parsing error within a { } command group do not
set the error cause to unmatched brace.
|
|
<Enter> now searches for lines starting with command delimiters to
find the command boundaries.
To actually enter a literal new line use <Ctrl-v><Enter> in insert
mode or `o` / `O` in normal mode.
Also remove the special <Backspace> mapping, does not seem esential
use <Escape> to close the prompt window.
|
|
A cursor does not necessarily have to be at a selection boundary
(e.g. in visual line mode) but it has to be within the selection.
|
|
|
|
|
|
They are roughly equivalent, instead of
s/pattern/replacement/
to replace the first occurrence of pattern you can specify an address
to the change command:
/pattern/ c/replacement/
the only difference being that the first command is restricted to the
current line.
-+x/pattern/ c/replacement/
also restrictes matches to the current line, but performs the substitution
on the whole line not only the first match. Currently it is not possible
to only replace the n-th match as `s2/pattern/replacement/` would do
in sam(1).
A possible alternative syntax generalizing this concepts and applying
it to the `x` and `g` commands will be investigated in the future.
Global substitution as in
%s/pattern/replacement/g
can be performed using
x/pattern/ c/replacement/
|
|
Before the i, a, c commands would fail when given an empty text //.
|
|
& refers to the most recent complete match and \1 - \9
refer to the last sub-expression matches.
|
|
These are currently only updated for `x` and `y` sam commands,
whether they should be updated for other search related activities
(`/`, `?`, `n`, `N`, `*`, `#` etc.) needs to be investigated.
|
|
|
|
We generally omit parameter names in function prototypes when their
meaning is clear.
|
|
This is akin to sam where dot is set to the result of a command.
|
|
At least one cursor (referred to as primary or main cursor) has always
to exist. In the sam command language implementation we might want to
dispose a cursor even if it is the primary one before later commands
will create different ones (e.g. `:x/pattern/ { i/>>>/ a/<<</ }`).
This commit introduces view_cursors_dispose_force. If called on
the last remaining cursor, its selection is cleared and it is marked for
destruction as soon as a new cursor is created. view_cursor_disposed
returns the cursor marked for deletion (if any) and clears the descruction
flag.
|
|
|
|
Send SIGSTOP to process group. This should fix job control when
launched from a script.
|
|
This allows to create a self extracting executable. The standalone
binary and lua files are extracted to /tmp/.vis-XXXXXX, vis is started
with the given command line arguments, finally temporary files are
removed.
Signed-off-by: Christian Hesse <mail@eworm.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Capacity also needs to be reset.
|
|
For some reason we ended up with two identical functions: buffer_{clear,terminate}.
|
|
Do not restore color palette for :! commands (i.e. in ui_terminal_save).
By far the most common use of this is to invoke vis-menu(1)
(e.g. indirectly through `:open .` or for word completion).
Restoring the palette in this case also affects the file content still
being visible above the menu thus causing weird display artifacts.
Use the OSC 104 escape sequence to reset color palette. This should
respect custom color profiles.
|
|
|
|
|
|
|
|
|
|
|
|
|
