| Age | Commit message (Collapse) | Author | Files | Lines |
|
This is a Lua 5.2 feature supported by LuaJIT.
|
|
Operate on the next number to the right of the cursor,
for now the matches are not restricted to the current
line.
Based on a patch from Denis Warsow.
Close #509
|
|
|
|
It remains to be seen whether that is a good idea, but at least
it will reveal possible bugs.
|
|
Based on a patch by Denis Warsow.
Stuff which could probably be improved:
- in vim the cursor does not need to be on top of the number,
it suffices to be on the same line.
- decrementing beyond zero does not work for hexadecimal and
octal numbers, vim seems to wrap around in this case.
0x00000000 <C-x> becomes 0xffffffff
Close #506
|
|
Load a standard plugins directly from vis-std.lua.
|
|
Stuff which was left out / our local changes include:
- lexer.lua: different loading mechanism and style handling
- ansi_c.lua: for now we keep the separate token definitions
with references to the respective standards.
This should highlight file names after #include directives.
It will also treat simple, non-nested occurrences of
#if 0 ... #endif as a comment.
- pkgbuild.lua: the arch specific fields have been kept
- all scintilla $(style variables) have been replaced
|
|
|
|
|
|
|
|
This allows lines like
: ${FOO:="${bar}/baz"}
to be highlighted correctly.
|
|
This should fix #412 properly.
|
|
Commit 3570869c removed the lexers sub directory from the Lua search
path. Update the comment and readme to reflect this change.
|
|
Terminal.app sets $TERM=xterm-256color and ships a corresponding
terminfo description advocating that it is capable of color changes
to the 256 color palette when in fact it can not.
We introduce a new boolean option "change-256colors" which is
true by default but can be used to disable color changes. It is
automatically set if Terminal.app is detected using $TERM_PROGRAM.
This should fix display artifacts as described in #456.
|
|
Hook it up via Lua to <C-k> in insert and replace mode.
Close #460 #475
|
|
|
|
|
|
The most apparent change is that NULL is now also highlighted,
the themes might need to be tweaked a bit.
Based on an initial patch by Christian Hesse.
Close #307
|
|
Close #466
|
|
|
|
|
|
|
|
|
|
Differentiate between the case where the module is not found and
the case where an error occured while loading it.
This should make it easier to debug cases in which there is a
Lua version mismatch between vis and lpeg.
|
|
Close #429
|
|
This should fix isses with `crontab -e` editing.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The init event is emitted immediately after `visrc.lua` has been sourced, but
before any other events have occured, in particular the command line arguments
have not yet been processed.
Close #422
|
|
The editor core calls into the functions registered in the `vis.events`
table which then multiplex the events to all registered event handlers.
The first handler which returns a non `nil` value terminates event
propagation.
|
|
The following structure is adapted:
* visrc.lua entry point for all Lua code
* vis.lua only implements the Lua part of the core API
* vis-std.lua registers standard event handlers (e.g. syntax highlighting,
statusbar handling, theme changes etc). It is sourced from vis.lua.
* plugins/* non essential editor functionality, needs to be explicitly
enabled by loading it from visrc.lua
|
|
Also remove the lexers sub directory from the Lua search path.
As a result we attempt to open fewer files during startup:
$ strace -e open -o log ./vis +q config.h && wc -l log
In order to avoid having to modifiy all lexers which `require('lexer')`
we instead place a symlink in the top level directory.
$ ./configure --disable-lua
$ rm -rf lua
Should result in a source tree with most lua specifc functionality
removed.
|