| Age | Commit message (Collapse) | Author |
|---|
|
It can only install one package at a time.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It does not really fit into the style of the rest of
the command language. Eventually we should be able
to express this kind of thing using a looping construct
based on the `X` and `Y` commands.
|
|
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.
|
|
|
|
Since vis.lua now loads a standard set of plugins, we do not need
to include the visrc.lua file which might contain user specific
changes.
|
|
Before cebb24b36ac45cc7c6912481cacd29ef9d5c68b9 a mark
at the start of the file was treated specially to always
return position zero.
Since this was no longer the case the following would
insert text before the visible area:
<PageDown><PageUp><PageUp>ifoo
|
|
There are still issues with left shifts starting from
characterwise visual mode when the selection boundaries
are deleted. For now this is considered a pilot error.
Fix #508
|
|
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.
|
|
Returning true from the event handler, indicating that the
keys were consumed, should now prevent insertion as mentioned
in the documentation.
vis.events.subscribe(vis.events.INPUT, function(key)
if key == ' ' then
-- do something fancy here
return true
end
end)
|
|
|
|
|
|
|
|
If the user wants new files to be created as 600, they will have set
their umask to 077 in their environment. vis shouldn't restrict this
further than the user has configured.
|
|
POSIX says that
The mkstemp() function shall use the resulting pathname to create the
file, and obtain a file descriptor for it, as if by a call to:
open(pathname, O_RDWR|O_CREAT|O_EXCL, S_IRUSR|S_IWUSR)
So this umask change didn't do anything in practice, unless the original
umask was more restrictive than 0177.
|
|
|
|
Fix #505
|
|
This should fix selection changes after shift operators
in visual mode. The problem was that the NOP motion which
is executed when switching back into visual-line mode
destroys the selection if the cursor is not already placed
on a selection boundary.
Fix #501
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
Only extend end of range when the motion did so too.
As an example this prevents motions like `$dg_` from deleting the newline
which was the starting position.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The macro replay code has since been refactored, making this
obsolete. There is only ever one input queue from which keys
are interpreted.
|
|
$ ./configure --disable-help
shrinks the binary by about 20K on a x86_64 system.
|
|
|
|
Previously the window content would not be scrolled down when
inserting a newline exactly at the start of the display area
as in the case when a file starts with an empty line and the
following is performed:
<PageDown><PageUp><PageUp>o
|
|
Change the text_iterator_char_{prev,next} functions to treat
them as a single character, meaning cursor motions will skip
both bytes at the same time.
|
|
In a file with windows style \r\n line endings scrolling
up would wrap around to the end of the file.
|
|
|
|
|
|
The vim version installed on the Travis macOS VMs does
not seem to correctly handle ; when already on a matching
position. Move the affected test to test/vis.
Also fix white space related issues in sed invocation.
|
