| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
The ordered list of paths for startup and lexer files is:
- $VIS_PATH/{,lexers}
- $XDG_CONFIG_HOME/vis/{,lexers} (defaulting to $HOME/.config/vis/{,lexers})
- /usr/local/share/vis/{,lexers}
- /usr/share/vis/{,lexers}
- package.path (standard lua search path)
|
|
|
|
Holding down <Backspace> at the end of the file should not
keep the cursor on the middle line of the window.
|
|
The last new line is added to the cell matrix but failure
is reported to indicate that there is no space left for
further characters.
|
|
This for example now correctly displays tab characters at
the very start of the visible area.
|
|
|
|
|
|
|
|
Lua support can now be disabled at compile time using:
$ make CONFIG_LUA=0
This commit also adds an initial Lua API and provides a few
default hooks.
We now also require Lua >= 5.2 due to the uservalue constructs.
In principle the same functionality could be implemented using
function environments from Lua 5.1.
|
|
|
|
|
|
|
|
Faust is a DSP (digital signal processing) programming language.
See http://faust.grame.fr/
Closes #125
|
|
|
|
|
|
|
|
The only used event handler was used to update the '< and '>
marks which is now taken care of by the leave handler of the
visual modes.
|
|
A call to vis_prompt_show will now automatically switch to prompt
mode. Within the prompt leave/enter handlers the focused window
(vis->win) will still point to the document window not the one
referring to the prompt.
The selection marks '< and '> are now only updated when a visual
mode is left.
|
|
|
|
|
|
|
|
|
|
|
|
Use view cell matrix data to create the cursors on more appropriate
positions.
Closes #108
|
|
It currently works by switching to visual mode and then opening
the command prompt with a default range which refers to the
currently active selection.
|
|
The return value of operator implementations denoting the new
cursor position is interpreted in the following way:
- EPOS dispose the cursor
- [0, text_size] place the cursor accordingly
- otherwise i.e. > text_size keep the cursor position unchanged
The newly introduced last case is useful for operators which
are called from visual mode, but do not want to change the current
selection.
|
|
|
|
|
|
|
|
|
|
The signedness of char is implemenation defined, calling the is*
type of functions with negative values leads to undefined behaviour.
|
|
|
|
They now belong to the cell holding the corresponding regular
(i.e. non-combining) character. This also means that at least
in theory a cell could hold arbitrary amounts of data, in
practice it is limited to 16 bytes.
|
|
They currently consider any character for which wcwidth(3)
return 0 as a combining character.
|
|
Do not simply double the requested size. Instead take the maximum of
- the requested size
- double the current buffer size
This will use less memory for large register operations (e.g. deleting
the whole file).
|
|
At the start of text_save_range we stat(2) the file to check whether
we have currently mmap(2)-ed it. Then we proceed to write the new
file content which changes modification time. Hence we have to
stat(2) again to retrieve it.
This should fix spurious warnings about file changes outside the
editor when editing e.g. symlinked files.
|
|
Make sure that the (new) primary cursor is visible after removing
the last matched selection.
|
|
We need to properly skip partial matches (i.e. not whole words).
Closes #118
|
|
Closes #116
|
|
There are some combinations (e.g. line wise selection / character
wise register content) which should probably be improved further.
Also since vis currently neither supports the numbered registers
"0 - "9 nor the small delete register "- the deleted text is
not stored in any register. Notice that we can't call op_delete
in the implementation because it would overwrite the register
content we want to paste.
Closes #113
|
|
If the current $TERM value indicates 256 color support fall back
to xterm-256color otherwise try xterm.
Improves upon 43605fded457cec954600b688d54242341eedc7c
Closes #105
|
|
Increase the number of bytes to consider for syntax highligthing
before the visisble area. This should improve the handling of long
block comments.
Closes #110
|
|
Closes #109
|
|
This improves behaviour for unknwown/unrecognized terminals
as is the case for self contained binaries built with
"make standalone" which only includes a fixed set of terminal
descriptions.
Of course the terminal capabilities won't match, which will
likely cause some display issues.
|
|
Ref: http://purelang.bitbucket.org/
Closes #106
|
|
|
|
Closes #104
|
|
|
