| Age | Commit message (Collapse) | Author |
|
|
|
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.
|
|
|
|
Still hopefully that it will eventually become accessible again.
After github reverts the flagging of my account. For now I have cloned
it locally just in case.
|
|
|
|
By now we have efficient forward searches using the TRE regex backend.
Further improvements can be discussed in #488.
Close #260
|
|
While memory consumption should be improved, backward searches
will still be slow, because they are implemented in terms of
repeated forward searches. It needs to be investigated whether
the underlying automaton can have its transitions reversed and
essentially run backwards, as is the case in sam.
|
|
Reference external manual page and Lua API documentation.
This is still work in progress the piece table documentation should
probably also be moved somewhere else.
|
|
|
|
Close #407
|
|
Make the delay used to distinguish between an <Escape> key and
other terminal escape sequences such as for the Meta key run
time configurable. The value is given in miliseconds and defaults
to 50ms.
Notice that terminal multiplexers like dvtm or tmux might also
induce some delay which has to be configured independently.
|
|
The first argument is the file object while the second argument denotes
the full path to which it will be written. Path might be `nil` if the
file is going to be written to stdout.
The Lua function is expected to return a boolean value indicating whether
the write operation should proceed or be aborted.
|
|
The passed path can be different from file.name for instance when
opening a file `a` and then doing `:w b` where file.name will be the
former and path the latter.
|
|
Indicating that the event is triggered *after* a successfull write.
|
|
Except for special commands like `w` and `wq` treat the cursor
as an implicit one character selection to which the command is
applied.
|
|
|
|
Wether `/usr/local/share/vis` or `/usr/share/vis` is used depends
on how the configure script was invoked. However, both are never
used at the same time.
This section should be completely reworked at some point.
|
|
|
|
|
|
|
|
Also rename underlying C code.
|
|
It was the only command option which needed `=` to assign a value to.
This unifies the argument parsing logic and adds the possibility to
specify a per-option help text.
You might want to adapt your visrc.lua configuration accordingly.
|
|
|
|
|
|
|
|
|
|
Triggered after the new file content has been written to disk.
|
|
The event is only triggerred for new files read from disk (e.g.
splitting an existing window will not cause an event to be emitted).
|
|
|
|
Let vis_keys_feed always have an immediate effect. Previously,
if called from a key input handler the keys would just be added
to the input queue and processed once the current key handler
returned.
This also affects the exposed Lua API.
|
|
Close #353
|
|
|
|
|
|
|
|
|
|
It is a string in `git describe` format, as reporte by `vis -v`.
|
|
|
|
|
|
|
|
Based on a patch by Josh Wainwright.
Close #306
|
|
|
|
|
|
|
|
The intention is that vis.lua will provide parts of the Lua API not
implemented in the C core.
Please update your existing visrc.lua configuration file accordingly.
|
|
|
|
|
|
|
|
|
|
|
|
The following registers `:foo` as a command which prints a few things to
stdout:
vis:command_register("foo", function(argv, force, win, cursor, range)
for i,arg in ipairs(argv) do
print(i..": "..arg)
end
print("was command forced with ! "..(force and "yes" or "no"))
print(win.file.name)
print(cursor.pos)
print(range ~= nil and ('['..range.start..', '..range.finish..']') or "invalid range")
return true;
end)
|