| Age | Commit message (Collapse) | Author |
|
`operator` variable matches "#", leaving nothing for the comments rule
to match. Since "#" only marks comments in TOML, I just went ahead and
removed the character from the `operator` token.
|
|
According to the TOML github page[1], indentation can be tabs *and/or*
spaces, so `indent_error` is removed.
[1] https://github.com/toml-lang/toml#example
|
|
The function lua_pushstring can throw an error, meaning it
will setjmp(3) out thereby leaking the allocated memory.
By using lua_newuserdata we let Lua free the memory during
a GC run.
|
|
|
|
The following exit statuses are used:
0 an item was successfully selected
1 the selection was cancelled
>1 failure, some error occured
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Make macro definitions and enums available to debugger.
|
|
|
|
|
|
|
|
The core vis code was originally written under the assumption that there
always exists at least one window. However, when being called from the
Lua configuration file during start up this is not yet the case.
In general, Lua code should always be placed within appropriate event
handlers e.g. vis.events.INIT for global configuration. Invoking API
functions depending on an active window from top level statements is
not supported. Where before the editor simply crashed, these changes
turn such code sections into NOPs.
Fix #561
|
|
|
|
We keep a running docker container in the background. If the build
process fails this becomes dangling. Make sure the container is properly
killed.
|
|
If the existing primary selection is not a word, switch to a literal
search. This should still avoid unwanted prefix matches (e.g. when
renaming related variables) but allow searching for arbitrary regions.
Fix #746
|
|
Introduce utility function to create new anchored, primary selection.
|
|
Otherwise the config.mk file generated by ./configure does not end up
in the source tree and has no effect. Our Makefile does currently not
support out of tree builds. Previously this worked because the WORKDIR
within the Dockerfile was set to the vis source (and build) directory.
|
|
Adapt in_tag to surrounding coding stlye and use the same simplified
version in html, wsf and xml lexers.
|
|
the new pattern does more or less the same thing, but forward
instead of backward.
|
|
|
|
|
|
Fix #665
|
|
|
|
|
|
|
|
These are reported by:
mandoc -T lint
|
|
|
|
|
|
This should catch Alpine package changes such as the one fixed in
0ba252f08e9ef7b62c442eb91b36822d654f5b04.
|
|
|
|
This allows to build with docker-compatible container engine:
make DOCKER=podman docker
|
|
This removes the docker image and volume `vis` and thus purges everything
we added in docker.
|
|
|
|
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.
|
|
|
|
|