| Age | Commit message (Collapse) | Author |
|
This can for example be used to abort git commit messages with :q! 1.
|
|
Starting with mandoc version 1.14.2 the xhtml format is no longer an
alias for html.
|
|
|
|
Close #761
|
|
Special case <C-v><Enter> to still insert a carriage return as discussed
in #656 and changed in 2cfc9c867bdfd4cc3ae3246f31cf636633fe1a5f.
Due to limitations of the current implementation <C-v> is not generic,
i.e. combining it as r<C-v><Enter> will not work.
Fixes #765
|
|
|
|
TODO: keys should only be highlighted in {} mappings.
|
|
|
|
When saving a file by atomically renaming it to its final destination,
we fsync(2) the parent directory to make sure the new directory entry
is persisted. However, not all file systems support fsync on file
descriptors referring to directories. As a result the save operation
fails and subsequent attempts result in warnings regarding outdated file
content, even though the data has most likely been successfully written.
Ignoring this particular error seems fine, because it is a permanent
limitation of the file system and not a temporary failure.
Fixes #792
|
|
Previsouly a command like:
x/^.*\n/
would only select every second line.
Fixes #774
|
|
This fixes empty backward searches ?$ starting at the line end.
|
|
|
|
|
|
No need to explicitly specify "lay" as an abbreviation,
since "layout" already makes it available via prefix logic.
|
|
Previously, searches wrapping around did not report any results if they
started from within the eventual match. Fix this by enlarging the search
area to the whole text after reaching the first boundary.
See also #787.
|
|
The regex anchors ^ and $ must not match at the start/end of the search
range unless it is preceded/succeeded by a new line.
This is implemented at the text-motion layer by passing the appropriate
REG_NOT{B,E}OL flags to the search backend, meaning the caller can
influence the anchor behavior depending on the context. This is important
as for example in the command language the anchors apply to existing
selections, not line boundaries.
|
|
|
|
|
|
|
|
|
|
|
|
This makes sure the feature is enabled as expected.
|
|
|
|
Commit 50b0a580105ac976a1c95df9441d898d7a652bfb updated Alpine docker
image, however this broke building with acl support. The static libacl
moved to its own package, so just install that.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Check for end-of-text.
|
|
1) “$” matches in the middle of the text.
visvis
^ - standing here
\/ - at first we search forward-\
\_/ - wrap, if nothing found <---/
After wrapping, in the second range “$” will treat end of the range
as EOL so “/vis$” will wisely match and moves cursor to the first
column.
2) No match after wrapping.
vissssss
^^ - standing here or here
\\____/ - search this before wrapping ---\
V - search range after wrapping <--/
“/vis” will *not* match (after wrapping), because it crosses ranges.
---
So the real solution would be that instead of the end position, the
start position of the possible match should be limited because a match
can cross the search ranges. To keep things simple, simply search two
whole text after wrapping.
visvis
\____/
|
|
|
|
|
|
Otherwise, show-{tabs,newlines,spaces} replacement characters are
undistinguishable from normal text.
|
|
- Fixed order of rules.
- Some “keywords” were identified as “type”, now corrected.
- Added compiler-specific common __keywords.
- Added boolean and additional integer constants.
- Added support for number suffixes.
- Removed “#if 0“ comments, because it needs some work on the else
branch.
|
|
|
|
Apparently plan9port is no longer included in homebrew:
https://github.com/Homebrew/homebrew-core/pull/38394
|
|
|
|
|
|
|
|
Otherwise, a file like `passwd.c` will match both ansi_c and dsv.
The one that gets chosen depends on the iteration order of table,
which is non-deterministic.
|
|
This introduces a new `set` option for setting the layout to
vertical or horizontal, which previously could not be done
without creating a new window (via `split` or `vsplit`).
Now, `set layout|lay h|v` will control this without creating
a new window.
|
|
|
|
|
|
Or else the following:
<<EOF
....
EOFXYZ
parsers incorrectly.
|
|
|
|
|