| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
|
|
|
|
|
|
No longer accept "no" prefix for boolean options. Reject too many option
values (use proper quoting to specify values containing spaces).
|
|
|
|
We first try $SHELL and then fall back to the shell field of the password
file entry (/etc/passwd).
|
|
:0 < echo "Should be inserted at the start of the file"
:1 < echo "Should replace the first line"
|
|
|
|
|
|
Also rename underlying C code.
|
|
It was the only command option which needed `=` to assign a value to.
This unifies the argument parsing logic and adds the possibility to
specify a per-option help text.
You might want to adapt your visrc.lua configuration accordingly.
|
|
|
|
|
|
|
|
|
|
|
|
Do not alter the text if <Escape> is pressed instead of a regular
replacement character.
|
|
|
|
Includes the new ssam(1) based tests.
|
|
|
|
The `git describe` command fails in shallow checked out git repositories
which do not include the tag information. At least include the git short
hash.
|
|
In normal mode `r<key>` was previously implemented as `R<key><Escape>`.
However this does not work when the replacement key is `<Enter>` to insert
a new line, because in replace mode new lines are not overwritten.
The count is now also respected.
Also properly support `r` in visual mode where before it was aliased to `c`.
Fix #190
|
|
Do not take snapshots after every operation in insert/replace mode.
As an example up until now we would take a snapshot after every
<Backspace>/<Delete> press, hence when undoing changes each character
would be restored individually. The same applies for <C-w> and related
actions.
From now on we only snaphost when:
- transitioning from insert/replace mode to normal mode (but not when
switching to operator pending mode)
- an operation takes place from normal mode
- an idle time expires in normal/replace mode
|
|
Delete the given range and insert the same number of replacement characters.
|
|
They both perform a motion before changing mode.
|
|
We need to distinguish between an explicit given zero and an
omitted value which should default to 1.
This should fix the following constructs which rounds up/down
an existing selection to whole lines -0,+0 and -0+,+0-
|
|
We should only attempt to parse special keys if they are
delimited by angle brackets i.e. <Key> but not Key.
Previously we would wrongly skip over the latter.
|
|
Something like :{ x/pattern/ } should not leave the original
cursor around.
|
|
Make sure that the view_cursors_scroll_to function does not enter
an infinite loop.
|
|
These paths are used to load the Lua LPeg module (lpeg.so)
and are thus helpful when diagnosing setup problems in case
syntax highlighting does not work.
|
|
The following
x/example/ y/e/ i/-/
should produce `-e-xample-` where before it would wrongly
result in `-e-xample`.
|
|
Previously something like
:x/pattern
:c/replacement
would cause all cursors to disappear because the location
they were placed on was deleted beneath them.
|
|
Something like :{ x/pattern/ } should select all occurrences of pattern.
|
|
|
|
Any white space should terminate the command name.
In particular multi-line commands as part of a group
were not handled correctly.
|
|
\\ should not be treated specially when parsing regular expressions.
|
|
When multiple selections are being displayed and the selection
orientation is changed, the complete primary selection was
wrongly colored in the style of the primary cursor.
|
|
In theory this should not happen in the first place, but in practice it
might fix the symptoms reported in issue #367.
|
|
The new code is preferable because it works independently of the
variable type. Whereas before a change in type, but not within the
sizeof expression would cause a wrongly sized allocation.
|
|
|
|
color mode
Setting the background color to the same color as the text is not
helpful, instead use red for the color column and underline to
highlight the cursor line.
|
|
Up until now only the background color could be changed.
|
|
See also discussion in #402.
|
|
We only remove leading but not trailing white space of the lines
to be joined. Not completely sure whether that is an improvement,
but it matches vim behavior.
Do not insert a space when joining empty lines.
|
|
The mapped to latin key has typically a shorter UTF-8 representation,
thus explicitly copy the NUL terminator to properly truncate the new
key value.
|
|
While the replacement symbols are still not run-time configurable,
the new defaults should hopefully please more people.
Close #401
|
|
The language map translation should not take modifiers into account.
For example if `a` is mapped to `b` then `<M-a>` should also be mapped
to `<M-b>`.
Fix #404
|
|
|
