aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2023-10-05fix literal makefile name detectionFlorian Fischer1-1/+1
The current literal file name detection for GNUmakefile, makefile or Makefile could match anywhere in the file name. For example the file type of `makefile.lua` (the name of our makefile lexer) was detected as makefile. This is fixed by requiring the literal patterns to start and end with the string.
2023-10-05vis-lua: fail when mapping a key to an invalid handler typeKarthin Srinavakili1-0/+2
When passing an invalid handler type (i.e., any type that isn't a string, function, or KeyAction) to Vis:map/Window:map, the editor would map the key to an empty (zeroed) KeyBinding struct. vis_keys_process() doesn't take this into account, so the key is never consumed from the input queue, causing the editor to get stuck in an infinite loop.
2023-09-27vis-complete: also split on `\`Randy Palamar1-1/+1
suggested in [0] since it will be help for latex [0]: https://github.com/martanne/vis/commit/dac6a7e#comments
2023-09-27filetype.lua: add common *roff extensionsTom Schwindl1-1/+2
2023-09-25vis-menu.c: add space for terminating NUL byteTom Schwindl1-1/+1
2023-09-22vis-subprocess.c: remove unnecessary NULL checkTom Schwindl1-3/+1
2023-09-22vis-complete: use hand picked set of characters for word splittingRandy Palamar1-1/+1
{w,}ctype(3) character classes are essentially broken for non-ascii text. 711447a tried to fix this for words surrounded by blanks but forgot the use case of completing function and variable names in source code. Instead of relying on the terrible ctype interface we can hand pick a set that is good enough for both source code completion and writing prose. This set is consistent with the old [:alnum:] behaviour for ascii text but also supports words with single width non-ascii characters. fixes 711447a: vis-complete: handle non-ascii text closes #1132: Source code completion are broken
2023-09-22vis-single: respect TMPDIREvan Gates1-3/+13
The temporary directory for vis-single was hard coded to /tmp. If /tmp happens to be mounted noexec then vis fails as it cannot run anything placed inside the temporary directory. If the TMPDIR environment variable is set, respect it for vis-single.
2023-09-20filetype: add psm1 and search for xml using mime typeMichiel van den Heuvel1-1/+2
2023-09-17vis-subprocess.c: fix signature of new_process_in_pool()Tom Schwindl1-1/+1
2023-08-27Make expandtab option window-localAlexey Yerin6-16/+16
2023-08-27Make tabwidth option window-localAlexey Yerin8-22/+19
2023-08-27lua: make sure lpeg is in fact optionalRandy Palamar2-0/+2
fixes #1119: lua: lpeg module isn't actually optional
2023-08-27vis-lua.c: silence warning about implicit conversionRandy Palamar1-1/+5
`SIZE_MAX` cannot be represented accurately in `lua_Number`. A correct solution probably doesn't exist but we can silence the warning by explicitly casting to `lua_Number` and changing the comparison to `<` instead of `<=`. checkpos() deals with large numbers for file ranges. For most users we can assume no one is editing files that are `SIZE_MAX` bytes long (many petabytes). For obscure systems where `SIZE_MAX` is a small number this will result in a maximum range (in lua) of 1 byte less than before. fixes #1120: vis-lua.c:504:21: warning: implicit conversion changes value
2023-08-26support old option names but mark as deprecatedRandy Palamar3-10/+24
This is in response to a comment left on a35e7ea. Backwards compatibility is a good idea for at least a release.
2023-08-25configure: also check for lua-5.4Donald C. Allen1-1/+1
2023-08-24lua api: fix a couple typos in process_response() documentationRandy Palamar1-2/+2
I thought I fixed these in the applied patch but I guess they slipped by
2023-08-24Implementation of the non-blocking process running Lua APIxomachine7-1/+350
Rationale A modern text editor usually includes tools for helping user to avoid mistakes in texts. Those tools include spell checkers and programming language integrations. Though vis explicitly states that the full featured IDE is not a goal, implementing some of the tools might be achieved using its Lua API. Unfortunatelly the API misses the ability to start a process and to perform a communication with it without completely blocking the editor UI, which is crucial for any tool that performs background tracking of the inserted text (e. g. language servers). Implementation details New feature introduces new API method: communicate. The method start a new process and returns a handle to communicate with the process instantly. The patch inserts stderr and stdout file descriptors of the process to the pselect call of the main loop used for reading user input to track the process state without blocking the main loop until the process is finished. Any changes in the process state cause the iteration of the main loop and are being exposed to the Lua API as new event: PROCESS_RESPONSE.
2023-08-24sam.c: rename a number of options to match lua apiRandy Palamar2-9/+9
2023-08-24Lua API: access and set all available optionsRandy Palamar7-27/+433
The first point of this commit is to allow all options to be read from lua. This has a number of uses for plugin writers. They are grouped into a couple of tables depending on what they control: `vis.options`: table with global configuration `win.options`: table with window specific configuration The second point is to allow you to set all these options as if they were simply lua variables. Technically this is already possible by using `vis:command("set ...")` but personally I think this interface is cleaner. Note that this already possible for some things like the current mode (eg. vis.mode = vis.modes.VISUAL). Examples: `vis.options.ai = true` `win.options.brk = " !?."` `win.options = { showeof = true, showtabs = true } There are a number of related issues and pull requests: closes #803: Lua API: let plugins read the values of options closes #812: Window layout property supersedes/closes #717: Add ability to access tabwidth from Lua supersedes/closes #1066: expose UI layout and allow it to be set from lua API
2023-08-17build: don't use the '|' GNU extensionRandy Palamar1-3/+4
2023-08-17build: don't pollute base dir with .o and .d filesRandy Palamar2-9/+11
some users were (rightfully) annoyed by this
2023-08-16build: stop setting _POSIX_C_SOURCERandy Palamar2-2/+2
from feature_test_macros(7): > Defining _XOPEN_SOURCE with a value of 700 or greater produces the > same effects as defining _POSIX_C_SOURCE with a value of 200809L or > greater. Depending on the configuration and system pkg-conf files there can be redefinition warnings. Rather than patching with a -U_POSIX_C_SOURCE it can just be dropped instead.
2023-08-16build: support incremental rebuildsRandy Palamar6-8/+22
2023-08-14vis-complete: handle non-ascii textSilvan Jegen1-1/+1
The '[:alnum:]' set does not include non-ascii text which results in the non-ascii text being replaced with newlines. Using the '[:blank:]' set with no complement flag fixes this issue.
2023-08-14vis-menu: try to preserve valid Unicode pointsSilvan Jegen1-3/+37
Before we were not taking non-ascii characters into account properly. With this patch we still mix byte counts and "grapheme cluster" (i.e. complete glyphs that are rendered in a terminal cell) counts but the code should be less broken in the more common case now.
2023-08-12ci: freebsd: use lua 5.3 like the othersRandy Palamar1-2/+2
2023-08-10vis-lua.c: stop obj_ref_get() from leaving the lua stack modifiedRandy Palamar1-17/+8
The only place where this behaviour was encountered was in file_lines_iterator() and it was just being worked around.
2023-08-07vim/test.sh: use ${CPP:-cpp} instead of hardcoding to cppHaelwenn (lanodan) Monnier1-1/+1
2023-08-07core/Makefile: Respect $CC and $CFLAGSHaelwenn (lanodan) Monnier1-1/+1
Related: https://bugs.gentoo.org/722014
2023-08-01Prevent flickering in cursesIan Hixson5-1/+26
Reading from curs_refresh(3X) from curses, calling doupdate() repeatedly will cause 'several bursts of output to the screen'. wnoutrefresh() has the smarts to only copy the changed lines to the copied virtual screen, but doupdate() does not. There have been several bug reports related to flickering but all seems to be inconsistenly reproducible due to different terminal buffering behavior. See #1032, #327 Unfortunately, when I am using a slow display, I still notice flickering, so this commit changes the routines for opening new windows and splitting windows to wait until the last change is finished before calling doupdate().
2023-08-01vis-open: allow to show files verticallyVadym Kochan1-1/+5
It might be more comfortable to navigate through the files arranged vertically. Add ability to specify VIS_OPEN_LINES environment variable which is passed to vis-menu as -l option. It would be better to add vis option for this to set it via lua config, but it might be added later. Signed-off-by: Vadym Kochan <vadim4j@gmail.com>
2023-07-28view.c: add word wrappingAndrey Proskurin5-30/+114
this is contolled by the wrapcolumn/wc and breakat/brk options related #142: Word wrap and line breaks related #932: Vis for Prose? related #1092: Disabling line wrapping
2023-07-28view: refactor view_addchAndrey Proskurin1-78/+78
2023-07-28Introduce new `mail` file type.Matěj Cepl1-0/+3
Aside from the possibility of future syntax highlighting (similar to https://github.com/vim/vim/blob/master/runtime/syntax/mail.vim in Vim). After objections on the list, I have decided not to include the conversion and user has to introduce it in their visrc.lua: vis.ftdetect.filetypes.mail.cmd = { "x/\r/ d" }
2023-07-18vis:pipe(): don't segfault if vis->win isn't presentRandy Palamar1-1/+5
When `file` was made optional the variable was changed to be initialized by `vis->win->file` instead of a known safe file pointer. If `vis:pipe()` is called based on the event `FILE_OPEN` the `file` parameter can be valid even when `vis->win` is not yet present. Assuming `file` was provided this would be handled later on if vis didn't segfault. By initializing to NULL when `vis->win` isn't present `file` is given a chance be handled later. In the case where `file` wasn't given and `vis->win` is missing an error is thrown and `vis:pipe()` exits. fixes #1107 - Lua API: vis:pipe() causes a segfault when called before a window is open
2023-07-18Add fullscreen param to vis_pipe_collect() and Lua API vis:pipe()Jörg Bakker10-18/+34
This enables restoring the terminal from a fullscreen command like curses based program. Use cases are e.g. a file picker based on some external program like nnn (https://github.com/jarun/nnn).
2023-07-18fix warning about field width not being an intRandy Palamar1-4/+4
this slipped through in commit 6be370d
2023-07-17Print keybindings containing space correctlyMax Schillinger1-2/+22
Fixes #1060 - :help doesn't display mappings starting with <Space> correctly Co-authored-by: Randy Palamar <palamar@ualberta.ca>
2023-07-16partial revert of commit f55312baJohn Vogel1-1/+2
text_paragraph_prev(): Bring back the previous usage of text_iterator_byte_get() in the while conditional and text_iterator_char_prev() in the loop body. Fixes #1028 - { moves back a paragraph too much if cursor at start of line
2023-06-22Lua API: allow nil in vis:pipe() File and Range parametersJörg Bakker1-5/+13
2023-06-22allow underscore (_) in command namesRandy Palamar1-1/+1
fixes #971
2023-06-21build: simplify generating single payloadChristian Hesse1-1/+1
We can make `od` skip the address radix, so `sed` does not need to remove it.
2023-06-09ci: update checkout action to v3Randy Palamar6-6/+6
2023-06-09ci: don't generate man/index.html symlinkRandy Palamar1-1/+1
this seems to be broken if the actor isn't the owner of the repository
2023-06-09vis-clipboard: don't fail when sel is primary on unsupported platformsRandy Palamar2-5/+2
this is mostly useful for the internal vis usage and makes both `*` and `+` registers work on macOS/cygwin. fixes: #1067
2023-06-08ci: strip owner name regardless of actorRandy Palamar1-1/+1
2023-06-08reword the :[v]split and :[v]new descriptions in vis.1Randy Palamar1-6/+6
(horizontally) and (vertically) were kept to be consistent with the 'v' mnemonic and with the enum labels in the code.
2023-06-08ci: fetch mandoc.css from release tarballRandy Palamar1-1/+1
this is more stable than grabbing from the CVS web interface
2023-06-06Limit to lines within range for inner text objectsMiles Canfield1-0/+3
You can read more about the author.