| Age | Commit message (Collapse) | Author |
|
|
|
Not sure why we need to allocate space for an additional character.
This also avoids creating out of bound pointers.
|
|
|
|
Previously calling die would segfault, e.g:
$ vis .
|
|
Newer gcc rejects multiple definitions of global variables.
Fix #21
|
|
Fix #830
|
|
Was also reported in #780.
|
|
|
|
Fix #825
|
|
Reorder the list rule such that it matches before the rule for code
blocks. There are still some problems with multiline list items which
are indented and wrongly matched as code blocks.
|
|
This should give the code block rule a chance to actually match
something, whereas before all leading white space was already
consumed.
Fix #823
|
|
Fix #824
|
|
|
|
Instead of clearing the whole screen and then moving the cursor to the
home position, we can first move it there and then clear everything
below it.
|
|
|
|
|
|
eg. if your long line is a comment with green fg, and you set your
column color bg red while not specifying the fg, then the result is
green fg on red bg.
Prior to this change the result would be default fg on red bg, thus
one char in the long line of green text would look odd/wrong.
Of course if you do explicitly set the column color fg to default in your
theme then the result will not be what you expect - ideally we need
an UNSPECIFIED color type instead of relying on DEFAULT.
|
|
|
|
Fix #820
|
|
|
|
When initially opened with a non-existing file we would not correctly
track the file's meta data resulting in spurious warnings upon subsequent
writes.
It is fixed by also saving the meta data for previously non-existing
files with matching paths.
|
|
Do not strip executables by default.
Fix #811
|
|
Otherwise the terminfo file for the default $TERM (xterm-256color) is
missing, causing vis to fail because libtermkey can not be initialized
properly.
|
|
|
|
macOS based builds are now run with Github actions.
|
|
Windows/Cygwin based builds are now run with Github actions.
|
|
By omitting the exact (minor) version number, this should be more
future proof.
|
|
Apparently the C.UTF-8 locale is not yet supported by upstrem glibc.
As a result this breaks the tests on distributions such as Arch Linux
which use unmodified glibc.
This reverts commit 92ee4fc43fd750246bbc1529082c0c0c8d9f233e.
Fix #20
|
|
|
|
|
|
|
|
Upper bound lexing time and cancel highlighting if it is exceeded.
|
|
|
|
barely noticeable CPU usage improvement, although the number of
iterations went down by an order of magnitude.
|
|
|
|
Add ! to override.
|
|
The modification time should only be compared when dealing with the
same file i.e. the following should work without a warning:
$ touch foo; sleep 1; touch bar
$ vis foo
:w bar
Also switch from path to inode based file equality testing.
|
|
|
|
|
|
|
|
|
|
|
|
A vis.events.FILE_SAVE_PRE callback may mutate the file text,
making the original range passed to cmd_write incorrect.
It is unclear how to realign the range after the callback
is done for the cases where an active selection in visual mode
is present or an explicit range like :1,2w! was specified.
However, this commit resolves the issue for the case where
the whole file is expected to be written.
|
|
The tests assert that the entire file text is written to disk
even if mutated in a vis.events.FILE_SAVE_PRE hooks.
|
|
The script named after <test-name>.lua, if exists, is run
just before loading and executing <test-name>.keys.
This allows tests to inject Lua code in the running vis instance
to help augment the test environment. For instance, a test could
listen to vis.events.FILE_SAVE_PRE events and mutate file text.
|
|
|
|
|
|
|
|
|
|
|