| Age | Commit message (Collapse) | Author | Files | Lines |
|
This makes sure that a successive view_update call returns
true and as a result the status bar will be correctly redrawn.
|
|
There is no longer a need to explicitly redraw the window status
bar upon a mode change, it will happen anyway during the next UI
update.
|
|
There is no need to treat the currently focused window specially.
|
|
We need to clear the info line before displaying a new message,
otherwise parts of the old cell contents might remain visible.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This ensures that the configuration at least compiles.
|
|
The intention of this is not to slowly reimplement curses but to provide
a minimal working terminal UI backend which can also be used for debugging,
fuzzing and in environments where curses is not available.
Currently no attempt is made to optimize terminal output. The amount of
flickering will depend on the smartness of your terminal emulator.
|
|
Use pull instead of push based model for display code. Previously view.c
was calling into the ui frontend code, with the new scheme this switches
around: the necessary data is fetched by the ui as necessary.
The UI independent display code is moved out of view.c/ui-curses.c into
vis.c. The cell styles are now directly embedded into the Cell struct.
New UI styles are introduced for:
- status bar (focused / non-focused)
- info message
- window separator
- EOF symbol
You will have to update your color themes.
The terminal output code is further abstracted into a generic ui-terminal.c
part which keeps track of the whole in-memory cell matrix and #includes
ui-terminal-curses.c for the actual terminal output. This architecture
currently assumes that there are no overlapping windows. It will also
allow non-curses based terminal user interfaces.
|
|
|
|
Close #513
|
|
The libtre5 package got approved / white listed for container builds in:
travis-ci/apt-package-whitelist#4023
travis-ci/apt-package-whitelist#4024
|
|
The same functionality is available using vis:command and :open.
If we decide a distinct API is useful, we should probably also
provide a corresponding close method.
|
|
|
|
This is no longer needed now that the completion logic was
moved to Lua.
|
|
|
|
The file name completion does not yet behave the same way as
the previous C code because the completion prefix is currently
simply calculated using the `iw` text object which does not
handle common path elements (e.g. `.`, `/`, `~`, etc).
|
|
|
|
|
|
|
|
|
|
Previously the following had no effect:
$ echo foo | vis +"set syntax markdown" -
Fix #512
|
|
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.
|
|
|
|
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.
|
|
|