kyx0r / nextvi Goto Github PK
View Code? Open in Web Editor NEWNext version of neatvi (a small vi/ex editor) for editing bidirectional UTF-8 text
Next version of neatvi (a small vi/ex editor) for editing bidirectional UTF-8 text
NEXTVI ====== Nextvi is a vi/ex editor. It can edit bidirectional UTF-8 text. NOTICE ====== As of 2022-01-01 Nextvi development has been driven to completion. No new features are being added, old ones polish and improve. Be sure to read Q1 in the FAQ section of this file before doing anything else. NAME ====== Nextvi tends to favor clean implementations over 100% adhering to POSIX like neatvi does. Thus the name "next", to signify that we are thinking outside the box. The notable changes that I am referring to (see below): 56, 60, 61. Some keybinds specified by POSIX were not implemented in original neatvi, nextvi might use them for some features below. NEATVI FEATURES --------------- - ex options: can be set using :se option or :se option=value can be unset using :se nooption td Current direction context. The following values are meaningful: * +2: always left-to-right. * +1: follow conf.c's dircontexts[]; left-to-right for others. * -1: follow conf.c's dircontexts[]; right-to-left for others. * -2: always right-to-left. shape If set (default), performs Arabic/Farsi letter shaping. order If set, reorder characters based on the rules defined in conf.c. hl If set (default), text will be highlighted based on syntax highlighting rules in conf.c. hll If set, highlight current line. ai As in vi(1). ic As in vi(1). - special marks: * the position of the previous change [ the first line of the previous change ] the last line of the previous change - special yank buffers: / the previous search keyword : the previous ex command - ex commands: :cm[!] [kmap] Without kmap, prints the current keymap name. When kmap is specified, sets the alternate keymap to kmap and, unless ! is given, switches to this keymap. :ft [filetype] Without filetype, prints the current file type. When filetype is specified, sets the file type of the current ex buffer. In nextvi :ft also reloads the highlight ft, which makes it possible to reset dynamic highlights created by options like "hlw". - new key mappings (normal): ^a searches for the word under the cursor. zL, zl, zr, and zR change the value of td option. ze and zf switch to the English and alternate keymap. gu, gU, and g~ switch character case. ^l updates terminal dimensions and redraws the screen. - new key mappings (insert): ^p inserts the contents of the default yank buffer. ^e and ^f switch to the English and alternate keymap. *vi(1) - for features unspecified refer to the respective page in the POSIX manual. NEXTVI FEATURES & CHANGES ------------------------- 1. Added unindent keybind: ^w ^w may also take vi_arg1 or motions as a region. 2. Added key to change the join mode of J key. keybind: vj Mode 1 (default) adds a space padding. Mode 0: raw line join. 3. Added linenumbers, keybind: # (relative numbers are placed after indent) Passing vi_arg1 to # enables permanent line numbers. 4. Added invisible character view, keybind: V 5. Added regex for changing spaces to tabs and vice versa, (controlled by vi_arg1) keybind: vi, vI 6. Added regex for removing \r line endings and trail space/tab, keybind: vo 7. Changed behavior of ^a to change search direction when no more match. (see 49.) 8. Added fssearch, searches what is under the cursor or (last search kwd) in every file in the opened directory keybind: ^] or ^5 By default it checks every file, else filter is specified by :inc (see 32.) This works in compliance with other changes (see 49. 58.) If max number of available buffers reached, the last buffer will be reloaded; losing potential unsaved changes. Use fssearch for code navigation between files, jump to definitions / etc. fssearch runs 40% faster than busybox's grep, benchmark tested (time to find something that doesn't exist) on the linux kernel. 9. fssearch but going in reverse keybind: ^p 10. Added key to create a global mark for the current buffer, keybind: ^t There are 5 global marks. vi_arg1 == 0,2,4,6,8 creates a global mark. vi_arg1 == 1,3,5,7,9 switches to the mark. 0 (default) is a special mark created by fssearch used by ^p as a return point for if ^p can't find any more matches. 11. Added ex command "ea" which opens file using filename substring. Setting an extra parameter in form of a number will tell how many matches with similar filename to skip. For example file might be named "./path/bla/bla/file123.c" but you can open it just by "ea fi" if this is a uniquely matched filename. 12. Added ex command "fd" to set and recalculate the directory listing for fssearch or "ea" ex command. No argument implies current directory. The "fp" command sets the path without recalculating. 13. Added numbered buffers to vi, default 10 and ex "b" command to show buffers and "b%d" to switch (where %d is the buffer number). Negative buffer numbers switch to temp buffers. Added new ex command "bx", where the argument will change the number of buffers allowed. If the number is lower than number of buffers currently in use they will be deallocated. Running bx without an arg will reset to default value. The default value is 10 or larger depending on the number of files specified in commandline arguments. Increasing the number of buffers may result in a positive effect on performance of fssearch (8. 9.) if the search keyword does not change. This is because vi will remember the position of previous match in the buffer avoiding redundant search. Improved buffer pathname expansion shortcuts. If you use character % or # in ex prompt they will substitute the buffer pathname. % substitutes current buffer and # last swapped buffer. Now it is possible to expand any arbitrary buffer by using % or # (no difference in this case) followed by the buffer number. Example: :!echo "%69" prints the pathname for buffer 69 (if it exists). % and # can be escaped normally if path expansion is not wanted. Added new ex command "bp" which changes the path for current buffer. For example :bp vi.c|e! will repurpose the buffer for vi.c Added new ex command "bs" which marks the current buffer as saved. Passing an arg will reset undo/redo history. Useful for scripting. 14. Added key to show buffers and switch buffer (to switch press corresponding 0-9 number) keybind: ^7 or ^_ If vi_arg1 is specified right before ^7 the buffer will be switched immediately which also happens to permit numbers > 9. 15. Added key to exit vi (not saving changes) keybind: qq or zz 16. Added key to goto first line keybind: gg 17. Added key to delete everything inside (cursor outside) "" keybind: di" or dc" 18. Added key to delete everything inside () keybind: di) or dc) 19. Added key to delete everything inside (cursor outside) () keybind: di( or dc( 20. Improved lbuf marks so they don't break under erroneous conditions. [] marks properly track the start and end of the insertion along with redo/undo. In addition, [] also track the horizontal pos. (only works with ` keybind) 21. Added a special substitution character ! which runs a pipe command. If the closing ! is not specified, the end of the line becomes a terminator. This makes any ex command be able to receive data from the outside world. Example: Substitute the value of env var $SECRET to the value of $RANDOM :). In this demo, we set the value of SECRET to "int" ourselves. :%s/!export SECRET="int" && printf "%s" $SECRET!/!printf "%s" $RANDOM! :) Commands :w and :r make internal use of '!'. Due to this, standard functionality would require escape. Examples: To send data use :w \!less To read data use :r \!date 22. Added new ex option "ish", this makes every "!" pipe command run through an interactive shell so that all shell features e.g. aliases work. By default it is enabled, can be disabled via :se noish Every ex command can use # % (see 13) and ! (see 21) substitution. Together, shell expansion is one of the most powerful features of nextvi. 23. Changed the colors to be based on standard ANSI 16 colors desc in conf.c Colors can be customized up to 256 colors if the terminal supports it. 24. Added new syntax highlighting for C, js, html, css, diff... 25. Added key that splits the line (opposite of J) keybind: K When vi_arg1 is specified, K will not create empty new line. 26. Added key that line wraps entire buffer to the 80 colon limit. keybind: gq The keybind only does 1 step, which means that multiple runs are needed if the lines are too long. Added key that line wraps a single line to 80 colon limit keybind: gq gq does as many steps as needed. Both keybinds estimate the word boundary such that words are not split. Both keybinds are macro, so set td=2 if there is bidi text, it makes a difference. 27. Added key that does multiline repeated edits keybind: v. This is based on the last commands and insertions and requires vi_arg1 for how many lines to repeat said operation. When last operation was 'i' or other commands that enter insert mode and some text, that text will be placed at the same offset on N number of lines specified by the vi_arg1. 28. Added ability to view the numbers for arguments that keys e,w,E,W,b,B may take. keybind: ^v Pressing again will change the key mode, specifying any vi_arg1 will exit the mode. This is a major step up to how navigation works in vi, it makes it so much easier to use because now you can see where you are going. These special numbers and their colors can be customized through conf.c. As of the latest git version, the feature will work correctly even if there is bidi text, double width characters and text reordering. 29. Added ability to change highlight dynamically. (via syn_reloadft();) 30. New ex option "hlw" which highlights every instance of word on the screen based on cursor position. Useful for when studying source code. 31. Added autocomplete in insert mode. Press ^g to index the current opened file. Then you can press ^n to cycle though the options, results are based on the contents of the file and the closest match to what you typed. Use ^r to cycle in reverse. By default, it will use big regex like [^;...]* to sort out all the punctuation chars from words and build a database of words. But in order to take full advantage out of the completion system, you can change this regex at runtime using new ex command "ac". For example say we don't want word completion and we want entire line completion instead, run :ac .* If the regex rule allows inclusion of nonalphanumeric or punctuation characters you won't be able to retrieve the string like it works with words by default. Automatically determining the position from which completion starts inside insert sbuf is ambiguous. More fine tuned control is needed and can be achieved using new keybind ^z in insert. Use ^z before you type out search term, this will set start position for completion, such that the options can be looped over inplace. ^z is a toggle, to disable it (without exiting insert) press twice in same place. When ^z is set ^u keybind will delete everything until ^z mark first, otherwise ^u operates normally (deletes everything). Autocomplete db is persistent throughout all buffers and it also has data duplication and redundancy checking such that same files can be indexed many times. Like ^g used to index file in insert mode, ^y can be used from insert to clear out the completion db. Running ex command "ac" with no argument will reset back to the default word filtering regex. You can find its string in led.c as a reference. Using ^b from insert mode will display all possible autocomplete options. Added new ex option "pac". When enabled the autocomplete options will be automatically displayed. 32. Added ex command "inc" which sets the path filter using regex. Example 1: We want to get only files in submodule directory that end with .c extension: :inc submodule.*\.c$ Example 2: Exclude the .git and submodule folders. :inc (^[\!.git\!submodule]+[^\/]+$)\|(<optional branch for exceptions here>) Running "inc" without an arg will disable all filters. 33. Added file manager temp buffer keybind: \ - The buffer can be edited with any directory listing, for example via :1,1!find . or filled using built-in methods such as :fd. see (32. 12.) - New ex command "cd" changes working directory according to 1st arg. - Added key that opens the file based on text from the cursor. keybind: ^i or TAB 34. Added key to save current file keybind: ^k 35. The new special character "/" for ft in conf.c now signifies that the regex will be applied on any file. "/" is forbidden filename character on unix, the filetype that includes "/" is for internal use. 36. Added a window size signal handler for vi to redraw the screen automatically. 37. Added history buffer for ex commands when in vi prompt. keybind: ^b or vb (from normal) will open the buffer with all previous commands move the cursor to wanted command and exit buffer with qq will copy the command into prompt. To immediately execute the command exit with zz. You can also use this when half-way through some command and need to access normal mode to edit the command more efficiently. The filename is named "/hist/" so that it can't be written to file with ^k (by accident). To save history to file use :w yourfilename 38. Added key to grab the current word(s) under the cursor into prompt like so :%s/.../ keybind: vr (see also 49.) 39. Added ex option to change number of spaces in a tab (\t) default is set to 8. use :se tbs=N (N is number of spaces) 40. Added partial support for multiline block regex, for example C multiline comments syntax highlight. 41. Made the lowest row to not waste any space when there are no messages and actually display the row. Passing vi_arg1 to ^g enables permanent status row. 42. Search via '/' or '?' automatically centers and redraws screen. This partly because change in 41 makes the bottom row behave dynamically and you might get search result on displayed on that row, which will be covered by search message instead. Also, centering is nice because you always know where to expect the result to be with your eyes. 43. Added terminal clean up on exit 44. Added a key to perform relative word replacements keybind: vt Specify vi_arg1 and the word(s) under the cursor will be placed into prompt, for example :.,.+5s/\<word\>/ where 5 is vi_arg1. (see also 49.) 45. Improved single line performance by roughly 3x. Syntax highlight will not render anything beyond the terminal columns. If there is a line in the file that has say 200K characters, the performance will not degrade (except the order option set, which is by default). Please do not underestimate the difficulty of such endeavor, nextvi is required to take all these operations into account: 1. Bidi text direction. 2. Multibyte UTF-8. Double width chars. 3. Variable width tabulations that can change throughout the line based on surroundings. 4. Reordering of characters. (regex rules) 5. Syntax highlight. No other text editor has ever done all these requirements at once, therefore come to appreciate what is provided here and the level of performance. See also PERFORMANCE section at the end of the file. Because syntax highlight is bounded to the terminal dimensions some patterns may not be possible to match without rendering past the screen. To address this problem you may need some extra patch, see PATCHES section below. 46. When in ex insert mode, exiting with ^c will discard changes. 47. Added Russian keymap, and changed how xkmap_alt works, now z + vi_arg1 in normal mode will switch what keymap ^f key changes, so for example 1 = fa 2 = ru. New language kmap can be added in kmap.h translation array. Added non printing characters to the list of digraphs. The naming resembles ASCII caret notation. For example, to type 03 (the literal for ^c) enter insert mode followed by digraph mode using ^k and type " c" without quotes. Additionally, literal can be typed using ^v as in vi(1). 48. Improvement to change 37. Now when in prompt/insert ^a will bring up the latest command from history. Also the history works for searches via / or ? the same way. keybind vv does the same but from normal mode, to save time. Pressing ^a again goes to next string. 49. Added ability to get more than 1 word for keybinds ^a ^] ^p vr vt v/ specified by number (vi_arg1). Regex control chars will be escaped. vr vt v/ ^] ^p will grab word(s) only if vi_arg1 >= 1 otherwise the keybind will perform a default cursor independent action. 50. Added ability to edit the line while in insert mode such that backspace can delete all the characters on the line, when no more characters left the line will be wrapped onto the next one. This is behavior you can expect from 95% of editors, now nextvi is not an exception. The similar change was done for ^w keybind. 51. Added key to show the registers and their contents. keybind: R If the length of a register is bigger than the terminal, specify vi_arg1 to to shift the printing position by half the screen size vi_arg1 times. 52. Made feature of reverse text highlight toggleable via new ex option "hlr" 53. Added a key to disable autoindent. keybind: va This is necessary sometimes if you want to paste from system clipboard. 54. Removed full names of ex commands and options, (seriously, who uses that?) now only short and fast to type abbreviations work. 55. Substitute undo-redo point return to where command was issued initially. 56. Modified regex engine to support static lookahead expressions. For example [!abc] and [=abc] where ! is negated version of =. This will treat "abc" as (a && b && c) logically. It is possible to have multiple in one bracket expression as well. For example [!abc!cda!qwe] where each string delimited by the ! acts like a typical or operation i.e. [acq] with only difference of testing the extra characters ahead. To combine both standard bracket expression and lookahead in one, use ^ or ^= where ^ is negated and ^= is default. For example: [!abc^=123] characters after ^= match exactly how [123] would. 57. Added ^l key in insert to clean the terminal and start at first line, remove distractions and focus on typing. Useful when running ex via vi -e 58. Added v/ key in normal, which can grab the current word(s) under the cursor into prompt and set the current search string. If valid, the input will be used for all search related operations in vi. (see 49.) 59. Added ability to remember scroll amount for ^e and ^y keys (specified by vi_arg1). Advantage of ^e and ^y over using ^u and ^d is keeping the same vi_col position. 60. Removed bracket classes from regex. Not useful, hard to customize, buggy, error prone mess. Doesn't add any new functionality to the regex engine that can't be achieved without it. 61. Nextvi special character escapes work mostly the same way everywhere except the following situations: - Escapes in regex bracket expressions. This isn't posix but it solves couple of issues that were bugged previously, like escaping | in ex substitution command, properly counting number of groups in rset. - # % and ! characters have to be escaped if they are part of an ex command - A single back slash requires 2 back slashes, and so on. - rset_make() requires for ( to be escaped if used inside [] brackets. - In ex prompt the only separator is "|" character. It can be escaped normally but will require extra back slash if passed into a regular expression. 62. Added syntax highlighting continuation options. See the struct highlight in vi.h. The ^ anchor in the regular expression has an important property of being able to efficiently exclude some sub expression from being recomputed during the continuation. Take advantage of it when you can. 63. New ex option "hlp", will highlight the closest pair of symbols {([ from the cursor, the same way % key works. This feature exists to demonstrate complex syntax highlighting capabilities. 64. Ex options "hll", "hlw", "hlp" fully customizable in conf.c on per ft basis the same way you customize per ft highlighting. They must have highlight->func struct member set. If ft does not provide a spot in hl, the latter feature will not work on that ft, regardless of ex options being set. 65. Added a key to quickly access :! prompt. keybind: v; Removed "make" ex command. Commands like these are not wanted, nextvi shall provide a more general purpose solution for the user, like the keybind v; for example. 66. Added new ex option "grp". The following allows definition of target search group for /?nN, (31.) autocomplete, (73.), and ex substitution. This becomes necessary when the result of regex search is to be based on some group rather than default match group. For example you want to search for the whole line but exclude the tabs at the beginning of the line, use regex like this: [ ]+(.[^ ]+) since only the capture result for 2nd group matters use the "grp" like this: :se grp=4 .The number 4 is important, it is calculated using: grpnum * 2, to get the second group number do: 2 * 2 = 4. The first group is always 2, 1 * 2 = 2, :se grp=2 gets you back to default group/behavior. 67. Undo and Redo commands (u,^r) may take optional vi_arg1 which repeats the operation N times. 68. Search motions do not terminate with error if the count is greater than number of instances found. Last possible match will be used. Important when you don't know exactly how many matches there are, does not mean there aren't any at all, greedy behavior opens up new use cases. 69. New ex command "tp", when arg given immediately executes the macro defined by arg. It can run any vi normal command and execute insert statements. The advantage of tp over traditional macros is in the ability to bypass the macro queue and run independently. In a way, macro executed by tp exercises the same causality as running C code directly. 70. Added key to list through the buffers. keybind: ^n vi_arg1 changes the direction of ^n. 71. In insert mode keybind ^o allows access to a secondary ex prompt or new vi instance so that it becomes possible to switch to vi from ex or postpone some operation, do something else and come back later. This feature is implemented using functionality provided by 69. and exists to prove and demonstrate that vi is to some extent REENTRANT as in single threaded recursion case, where operations can be safely executed in a separate instance. Still, a great amount of care and understanding is needed when making such complicated macros. 72. Added keybinds ^\ and ^] to control the default register for pasting (^p) in insert mode. ^\ selects any register or resets to default yank register if pressed twice. ^] changes register to the next available, between 0 and 9. Contents of the register are displayed on the bottom row. In nextvi, register 0 stores previous value of default register if operation is atomic and did not include a whole line, else register 1 takes its place. 73. New ex command :f allows for ranged search (stands for find). Example (no range given, current line only): :f/int or :f?int or (specified range) :10,100f/int Additionally, :f supports xoff (horizontal offset). This is essential for scripting macros. Subsequent commands within the range will move to the next match just like n/N. LESSER KNOWN FEATURES --------------------- - "Ever tried reading the source code?" Yes, that is a lesser known feature, what did you expect? Jokes aside (with a level of truth to it), these features exist in many other vi implementations but neither man pages cover their functionality in an understandable language, describe it here instead. - @@ macros: 1. Type out the macro or load from file such that it is in some vi buffer. 2. Use keybind "ayy on the macro, this will store it in register 'a' 3. Use @a to play it back, where a stands for that 'a' register 4. @@ repeats the last macro on next line - substitution backreference: This inserts the text of matched group specified by \x where x is group number. Example: this is an example text for subs and has int or void :%s/(int)\|(void)/pre\0after this is an example text for subs and has preintafter or void :%s/(int)\|(void)/pre\2after/g this is an example text for subs and has prepreafterafter or prevoidafter - ex ranges: Some ex commands can be prefixed with ranges. Example: print lines 1,5 :1,5p Example: print 5 lines around xrow :.-5,.+5p Example: print until int is found :.,/int/p Example: print until int is found in reverse :?int?,.p Note: in some cases . can be dropped but is kept for readability. Example: print lines from mark d to mark a :'d,'ap - ex global command: Same syntax as ex substitution command, but instead of replacement string it takes an ex command after the / / enclosed regex. Example: remove empty lines :g/^$/d Try doing similar with substitution command - will not work as removing '\n' without deleting the line is invalid, but it will work with global command. Multiple ex commands can be chained in one global command. In this case the ex separator has to be escaped once. Example: yank matches and print them out. :g/int/ya A\|p If you wanted to get really fancy, it is possible to nest global commands inside of global commands. Example: find all lines with int and a semicolon and append "has a semicolon" :g/int/:.g/;/tp A has a semicolon� - search motions: ? and / searches have the ability to be used as motions. This seems very counter intuitive and one would have never ever figure out that this feature even exists, unless noted. Even if you read the source code it's very easy to miss. How to use: optionally specify vi_arg1, specify the motion using its keybind, then do / or ? and type out the search term. The motion ends on the first match by default (no vi_arg1 specified). The optional vi_arg1 determines how many matches of the term to skip until the motion ends. Example: you see that the next 10 lines have the word "int" which is included 3 times. You want to delete text until the 3rd instance of "int" keybind would be 3d/int . Likewise you can opt out of the "specify motion" part and just use / or ? with vi_arg1 to perform specific searches. - Majestic EXINIT environment variable At the zenith of your vi/nextvi education you'll find that EXINIT can be used to achieve arbitrary level of customization. Using new ex command "tp" any sequence of vi/ex commands can be performed at startup. This is where real "groking vi" starts. Example 1: There is a dictionary file (assume vi.c), which we always want to have indexed at startup for autocomplete feature in 31. export EXINIT="e ./vi.c|tp i�|bx 1|bx" The last "bx" commands delete the vi.c buffer. To keep it around as a buffer remove the "bx" commands. Example 2: Load your shell's history into vi's history buffer and adjust the data such that it is usable by appending ! at the beginning of command and escaping the "|" pipes the way ex prompt expects them (see 61.) export EXINIT="e /root/.ash_history|tp yG:�p:%s/^/\!\\|%s/ \| / \\\\\\| /g qq|bx 1|bx|ft" Congratulations, vi has unofficially replaced your shell's frontend. Example 3: Setup some custom @@ macros in your favorite registers. export EXINIT="e|tp io{ }��kA|tp 1G|tp 2\"ayy" This macro gets loaded into register a, when @a is executed the macro will create { and closing } below the cursor leaving cursor in insert mode in between the braces. This is something you would commonly do in C like programming language. - CRITICAL - the new line inside the EXINIT string is literal, it's best to store the export command in a .sh file and set it using: $ . ./init.sh Otherwise this examples 2 and 3 may not work!!! To suppress EXINIT variable use -s commandline flag. - Uppercase registers In vi uppercase registers append to the lowercase register instead of overwriting the register completely. This is very useful, for example, use global and yank ex commands together: :g/searchterm/ya A Now we can use "ap and paste all the lines matched by the regex. Depending on the usecase simply :g/searchterm/ya or :g/searchterm/p may also be enough. PATCHES ------- New functionality can be obtained through optional patches provided in the patches branch. If you have a meaningful contribution and would love to be made public the patch can be submitted via email or github pull request. https://github.com/kyx0r/nextvi/tree/patches FAQ: ---- Q1: What's the best way to learn vi/nextvi? A1: First ensure you know basic movements hjkl this would suffice. Start reading vi.c don't worry about the rest of this readme until later. Running ./vi vi.c use / and n N keybinds for search and look for switch cases. The keybinds are encoded to be intuitive. Once you find some case that looks like a keybind read the code, if you don't understand try to reproduce the keybind to better understand what the code does. You have to do this, if you omit this step you will never be able to realize the full potential that the software provides. It's not desirable to live in the dark using this software for the next 10 years only to find that for example, ^p in insert mode exists and is very useful. If you can't figure how to use the keybind at least you would know at the back of your mind that there is something there, realization will come later. It's better to skim look through the switch cases than to never even open it. This isn't an excuse, but a deliberate design goal, where the user reads the code in order to achieve the full control he/she desires. LOC: +--------------+---------------------+ | 569 kmap.h | keymap translation | | 428 vi.h | definitions/aux | +--------------+---------------------+ | 577 uc.c | UTF-8 support | | 318 term.c | low level IO | | 298 conf.c | hl/ft/td config | | 652 regex.c | extended RE | | 590 lbuf.c | file/line buffer | | 1083 ex.c | ex options/commands | | 2085 vi.c | normal mode/general | | 685 led.c | insert mode/output | | 384 ren.c | positioning/syntax | | 6670 total | wc -l *.c | +--------------+---------------------+ The code is devised to be unquestionable. You will be able to read, understand and modify this code faster. Come back to this readme regularly as it documents more advanced behavior. Q2: What does it mean when I call feature X a macro? A2: It's the kind of shortcut that does not change the core functionality, but rather reuses the core functionality. Usually macro features are implemented in 1 or a few lines of code. Notably, they tend to use function term_push(), but it's not required. Because they are macros they may run suboptimally or not handle every possible edge case. When calling a macro feature from another macro, the results are pushed back, which means the macro feature will always execute last, with the exception of feature 69. These features are considered a macro: 5. 6. 16. 17. 18. 19. 26. 27. 34. 65. 71. Q3: Keybind with CTRL does not work? A3: vi is reading ASCII codes sent by the terminal. Depending on the keyboard, the ASCII code could be another key combination. It was reported that "^^" (Ctrl + ^) can be achieved on some system with "^6". If something doesn't work, have a look at the layout of an american/british keyboard and try to reproduce the keybind as if you have an american/british keyboard. Q4: Why nextvi instead of vim? A4: I prefer customization in source code, Vim is considered harmful. Q5: Why not distribute as patches, like on suckless.org? A5: It's hard to maintain. Simply put, there are too many changes to keep track of if compared to original neatvi. Q6: Why are keybinds encoded as pure switch cases instead of more suckless.org style keybind function table dispatch? A6: Because we want small efficient code that is easy to write. In nextvi many keybinds interoperate so that they can do multiple tasks at various conditions. Use of goto is encouraged, it is simply impossible to achieve this behavior in a sensible way otherwise. Suckless code style philosophy crumples when requirements are as complex as what vi needs to be able to do. In other words, it depends - but if the standard of C provides means to implementing things cleaner and faster you should use the smallest form factor possible. In retrospect, it may be harder to find the implementation itself, but once you do there is nothing else hidden from you. The result is unabstracted program control flow that can be easily read and modified reducing the risks of unforeseen side effects. Q7: General philosophy? A7: User is programmer, hacker culture. In most text editors, flexibility is a minor or irrelevant design goal. Nextvi is designed to be flexible where the editor adapts to the user needs. This flexibility is achieved by heavily chaining basic commands and allowing them to create new ones with completely different functionality. Command reuse keeps the editor small without infringing on your freedom to quickly get a good grasp on the code. If you want to customize anything, you should be able to do it using the only core commands or a mix with some specific C code for more difficult tasks. Simple and flexible design allows for straight forward solutions to any problem long term and filters bad inconsistent ideas. Q8: Something, something - pikevm A8: Pikevm is a complete rewrite of nextvi's regex engine for the purposes of getting rid of backtracking and severe performance and memory constraints. Pikevm guarantees that all regular expressions are computed in constant space and O(n+k) time where n is size of the string and k is some constant for the complexity of the regex i.e. number of state transitions. It is important to understand that it does not mean that we run at O(n) linear speed, but rather the amount of processing time & memory usage is distributed evenly and linearly throughout the string, the k constant plays a big role. If you are familiar with radix sort algorithms this follows the same idea. Q: What are the other benefits? A: For example, now it is possible to compute a C comment /* n */ where n can be an infinite number of characters. Of course this extends to every other valid regular expression. Q: New features pikevm supports? A: Additionally, pikevm supports PCRE style non capture group (?:) and lazy quantifiers like .*? and .+?? because they were easy to implement and allow for further regex profiling/optimization. Q: NFA vs DFA (identify) A: pikevm = NFA backtrack = DFA Q: What's wrong with original implementation? A: Nothing except it being slow and limited. My improved version of Ali's DFA implementation ran 3.5X faster in any case, however I found a bug with it where zero quantifier "?" nested groups compute wrong submatch results. To fix this problem, it would require to undo a lot of optimization work already done, basically going back to how slow Ali's implementation would be. The reason this was spotted so late was because this kind of regex wasn't used before, so I never tested it. Other than that I think submatch extraction is correct on other cases. Pikevm does not have this bug, so it will be used as main regex engine from now on, unless dfa ever finds a proper fix. Honestly, this change isn't so surprising, as I was working on pikevm a few months prior, to favor a superior algorithm. You can still find that code here (likely with no updates): https://github.com/kyx0r/nextvi/tree/dfa_dead As a downside, NFA simulation loses the DFA property of being able to quickly short circuit a match, as everything runs linearly and at constant speed, incurring match time overhead. Well optimized DFA engine can outperform pikevm, but that is rather rare as they got problems of their own. For example as independently benchmarked, dfa_dead runs only 13% faster than pikevm and that is stretching the limit of what is physically possible on a table based matcher. Can't cheat mother nature, and if you dare to try she's unforgiving at best. Supplementary reading by Russ Cox: https://swtch.com/~rsc/regexp/regexp1.html PERFORMANCE ----------- Stress test: 1. Compile both versions with gcc -O2 -g (no customizations done) 2. Open Nextvi's vi.c and hold ^d until the end of the file 3. Capture the results with cachegrind 4. To find out what these values mean see: https://valgrind.org/docs/manual/cg-manual.html NEATVI: -------------------------------------------------------------------------------- | I refs: 1,030,137,070 | I1 misses: 122,660 | LLi misses: 1,298 | I1 miss rate: 0.01% | LLi miss rate: 0.00% | | D refs: 672,331,702 (373,790,802 rd + 298,540,900 wr) | D1 misses: 473,511 ( 215,088 rd + 258,423 wr) | LLd misses: 7,836 ( 1,116 rd + 6,720 wr) | D1 miss rate: 0.1% ( 0.1% + 0.1% ) | LLd miss rate: 0.0% ( 0.0% + 0.0% ) | | LL refs: 596,171 ( 337,748 rd + 258,423 wr) | LL misses: 9,134 ( 2,414 rd + 6,720 wr) | LL miss rate: 0.0% ( 0.0% + 0.0% ) -------------------------------------------------------------------------------- NEXTVI: -------------------------------------------------------------------------------- | I refs: 364,197,180 | I1 misses: 93,186 | LLi misses: 1,228 | I1 miss rate: 0.03% | LLi miss rate: 0.00% | | D refs: 142,125,211 (100,909,090 rd + 41,216,121 wr) | D1 misses: 140,991 ( 81,656 rd + 59,335 wr) | LLd misses: 6,043 ( 1,855 rd + 4,188 wr) | D1 miss rate: 0.1% ( 0.1% + 0.1% ) | LLd miss rate: 0.0% ( 0.0% + 0.0% ) | | LL refs: 234,177 ( 174,842 rd + 59,335 wr) | LL misses: 7,271 ( 3,083 rd + 4,188 wr) | LL miss rate: 0.0% ( 0.0% + 0.0% ) -------------------------------------------------------------------------------- Further optimization: 1. To create the most optimal exe, enable PGO optimizations by compiling via ./build.sh pgobuild which can lead to a significant performance boost on some application specific tasks. Feel free to adjust build.sh and the sample data on which it's being trained on, though default probably already good enough. 2. To improve nextvi's performance, shaping, character reordering, and syntax highlighting can be disabled by defining the EXINIT environment variable as "se noshape | se noorder | se nohl | se td=+2". Favorite quotes: -------------------------------------------------------------------------------- "All software sucks, but some do more than others." - Kyryl Melekhin "Educated decisions assert the quantitative quality first." - Kyryl Melekhin "It’s possible that I understand better what’s going on, or it’s equally possible that I just think I do." — Russ Cox "Vigorous writing is concise. A sentence should contain no unnecessary words [and] a paragraph no unnecessary sentences, for the same reason that a drawing should have no unnecessary lines and a machine no unnecessary parts. This requires not that the writer make all his sentences short, or that he avoid all detail and treat his subjects only in outline, but that every word tell." — Elements of Style, William Strunk, Jr. - 1918 -------------------------------------------------------------------------------- CREDITS ============= Programming ------------- Kyryl Melekhin (kyx0r) Ali Gholami Rudi (aligrudi) Documentation / Design / Testing ------------- Kyryl Melekhin (kyx0r) Proofreading ------------- Kyryl Melekhin (kyx0r) Cédric (Vouivre) Special Thanks ------------- Ali Gholami Rudi (vi https://github.com/aligrudi/neatvi) ArmaanB (bsd test) aabacchus (build.sh) illiliti (build.sh) git-bruh (feedback) and all users, posters & haters :/
Is this possible (from the README, I don't think so, but I wanted to make sure)? If not, could you give a hint on how I could implement it (I'm not at all familiar with C)?
My use case is that I have shell scripts without extensions, but with "#!/bin/sh" at the start, and would like to trigger "sh" syntax highlighting for them.
In insert mode, when I type: 'x', enter, 'x', enter, backspace, backspace, backspace
, the second x remains until escape is pressed.
This is by far my favorite VI clone EVER! It's beautiful, simple, extensible, hackable, portable. It's exactly what I have been looking for for years.
Thank you for making this < 3
Hi Kyryl,
I had trouble to understand what was the ex option hll
. Now I understand better. The ex option hll
works perfectly with a c
file but not with a tex
file.
In a tex
it can happens that a line begins with a \
. For example:
\usepackage[T1]{fontenc}
\usepackage{geometry}
In that case, it doesn't work. In vi.c
the match is done by
syn_addhl("^.+$", 2, 1);
The .
matches any character but there is a problem with \
. Moreover, a line can have some spaces/tabs and then a backslash. The following can be found in tex
files:
\usepackage{xparse}
\begin{displaymath}
\end{displaymath}
\begin{displaymath}
\end{displaymath}
Where the spaces at the beginning of the lines can be spaces or tabs. Hhhhmmm, the following can also happen
This is some text with \textbf{boldface font} inside the text.
So I had changed
syn_addhl("^.+$", 2, 1);
to
syn_addhl("^([ | ]+)?(\\\\)?.+$", 2, 1);
In the class, there is a space
and a tab
. But it wouldn't work for the last example.
Do you have any idea how to match \
with a regex ?
Maybe some false positive of neatvi
test/e00.sh: OK
test/e01.sh: OK
test/e02.sh: OK
test/e03.sh: Failed
--- /tmp/.neatvi1 2023-06-14 00:16:03
+++ /tmp/.neatvi2 2023-06-14 00:16:03
@@ -1 +1,2 @@
abc
+def
OK
test/e04.sh: OK
test/e05.sh: OK
test/e06.sh: Failed
--- /tmp/.neatvi1 2023-06-14 00:16:03
+++ /tmp/.neatvi2 2023-06-14 00:16:03
@@ -1,5 +1,3 @@
abc
-abc
def
-def
ghi
OK
test/e07.sh: OK
test/e08.sh: OK
test/e09.sh: OK
test/e0a.sh: OK
test/e0b.sh: OK
test/e0c.sh: Failed
--- /tmp/.neatvi1 2023-06-14 00:16:03
+++ /tmp/.neatvi2 2023-06-14 00:16:03
@@ -1,9 +1,5 @@
1
2
-x
-x
3
4
-x
-x
5
OK
test/e0d.sh: Failed
--- /tmp/.neatvi1 2023-06-14 00:16:03
+++ /tmp/.neatvi2 2023-06-14 00:16:03
@@ -1,7 +1,5 @@
1
-x
2
3
-x
4
5
OK
test/e0e.sh: OK
test/e0f.sh: OK
test/e10.sh: Failed
--- /tmp/.neatvi1 2023-06-14 00:16:03
+++ /tmp/.neatvi2 2023-06-14 00:16:03
@@ -1,2 +1,2 @@
-xyz
-xyz
+abc
+def
OK
test/e11.sh: OK
test/e12.sh: Failed
--- /tmp/.neatvi1 2023-06-14 00:16:03
+++ /tmp/.neatvi2 2023-06-14 00:16:03
@@ -1,3 +1,3 @@
a
-z
+b
c
OK
test/v00.sh: OK
test/v01.sh: OK
test/v02.sh: OK
test/v03.sh: OK
test/v04.sh: OK
test/v05.sh: OK
test/v06.sh: OK
test/v07.sh: OK
test/v08.sh: OK
test/v09.sh: OK
test/v0a.sh: OK
test/v0b.sh: OK
test/v0c.sh: OK
test/v0d.sh: OK
test/v0e.sh: OK
test/v0f.sh: OK
test/v10.sh: OK
test/v11.sh: OK
test/v12.sh: OK
test/v13.sh: Failed
--- /tmp/.neatvi1 2023-06-14 00:16:03
+++ /tmp/.neatvi2 2023-06-14 00:16:03
@@ -1,3 +1,3 @@
ABC
-21DEF
-GHI
+1DEF
+2GHI
OK
test/v14.sh: OK
test/v15.sh: OK
test/v16.sh: OK
test/v17.sh: OK
test/v18.sh: OK
test/v19.sh: OK
test/v1a.sh: OK
test/v1b.sh: OK
test/v1c.sh: OK
test/v1d.sh: OK
test/v1e.sh: OK
test/v1f.sh: OK
test/v20.sh: Failed
--- /tmp/.neatvi1 2023-06-14 00:16:03
+++ /tmp/.neatvi2 2023-06-14 00:16:03
@@ -1,2 +1 @@
aa
-bb
OK
test/v21.sh: OK
test/v22.sh: OK
test/v23.sh: Failed
--- /tmp/.neatvi1 2023-06-14 00:16:03
+++ /tmp/.neatvi2 2023-06-14 00:16:03
@@ -1,5 +1,5 @@
+
a
b
c
-
a
OK
Line 2008 in 9e9d05a
Some people may want to customize their keybinding a little bit without spending hours looking "Oh I forgot to change this switch statement."
An example of that is changing hjkl
to characters used by other keyboard layouts (not languages, just layouts like colemak and workman), yneo
and neio
would be good examples.
A simple translation array should be enough for most uses.
Is there a way to wrap long lines?
What is happening:
+----------------------+
| |
| 1 some text in a line|
| 2 |
+----------------------+
+---------+
|too long |
+---------+
Wraping the line:
+-----------------------+
| 1 some text in a line |
| too long |
| 2 |
+-----------------------+
(I'm using st
)
I opened two buffers in neatvi and I tested the command you implemented to switch buffers: ^s.
As soon as I press "^s" vi freezes and I can do nothing. I have tested "^a" which works.
Just tell me if you need more information.
I read ":e! reedit, discard changes".
Is your implementation POSIX conform?
As I can see, there is no completion for filenames when a new file is opened. I don't mean completion in the buffer, but when the command
:e myfile
is executed. I also don't see an history system for the ex commands. It frequently happens I have to open a file which is in another directory, and the path is not very short. With a completion system, I can avoid a typo. If each time I have to write
:e path/mydocuments/2020/support/chemistry/exercise_24
I can expect to try to open it multiple times until there are no typo anymore. Not always, but it will happen.
Is it possible to implement something, or perhaps better, to have a workaround. I could imagine copying the path from a terminal or something like dmenu
.
You added a keybind for the filemanager hund
. Is the idea to open the filemanager and to use it to open the file in neatvi
?
Hi,
The syntax highlighting pattern for standard Python strings fails with embedded escaped quotes.
These two patterns produce the expected highlighting. I used separate patterns because it is easier for me to read.
{"py", "[\"]([^\"]|\\\")*[\"]", {4}},
{"py", "[']([^']|\\')*[']", {4}},
I used the following strings to test this.
"testing \"this\" embedded double-quoted"
'testing \'this\' embedded single-quoted'
Before this change, the word this was white; now the whole string is blue. I changed the number of backslashes.
Some people use triple-quoted strings when they need to embed quotes, or they use one type of quote outside and the other type inside, but not always - sometimes they escape the clashing quotes.
If this makes sense, please consider updating conf.c.
Thanks.
P. S. I am trying to understand how the highlight structure's end and blkend work. Please give me some hints.
I was told here that i could make backspace function like it does in vim. How?
It's annoying to have to reenter insert mode every time I use the arrow keys
Would you consider adding support for arrow key navigation? I'm used to using arrows in vim since it's nice to be able to move the cursor in insert mode. Thanks
I was wondering if it's possible to switch from variable length arrays to normal static arrays. I'm porting nextvi to 9front, and the compiler doesn't support them.
I have no idea how vim does it, so idk if it would work, but its worth at least looking at.
It's annoying that syntax highlighting doesn't work when editing files without the right file extension, for example, neofetch is a bash script, but since it has no file name extention, there is no syntax highlighting.
Hi. Thank you for the work you are doing.
There seems to be an issue with the last few commits.
This commit onwards, doing sudo make install
throws an error, which isn't so in the previous commits.
Here is the output:
$ sudo make clean install
rm -f *.o vi
cc -c -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L vi.c
cc -c -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L ex.c
cc -c -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L lbuf.c
cc -c -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L sbuf.c
cc -c -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L ren.c
cc -c -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L led.c
cc -c -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L uc.c
cc -c -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L term.c
cc -c -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L regex.c
cc -c -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L conf.c
cc -c -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L hund.c
cc -o vi vi.o ex.o lbuf.o sbuf.o ren.o led.o uc.o term.o regex.o conf.o hund.o -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L
/bin/ld: regex.o: in function `regexec':
regex.c:(.text+0x1b48): undefined reference to `brk_match'
/bin/ld: regex.c:(.text+0x21dd): undefined reference to `brk_match'
/bin/ld: regex.c:(.text+0x284d): undefined reference to `brk_match'
/bin/ld: regex.c:(.text+0x2ec6): undefined reference to `brk_match'
collect2: error: ld returned 1 exit status
make: *** [Makefile:11: vi] Error 1
And for the earlier commits that work:
$ git checkout fc92963
$ sudo make clean install
rm -f *.o vi
cc -c -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L vi.c
cc -c -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L ex.c
cc -c -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L lbuf.c
cc -c -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L sbuf.c
cc -c -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L ren.c
cc -c -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L led.c
cc -c -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L uc.c
cc -c -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L term.c
cc -c -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L regex.c
cc -c -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L conf.c
cc -c -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L hund.c
cc -o vi vi.o ex.o lbuf.o sbuf.o ren.o led.o uc.o term.o regex.o conf.o hund.o -pedantic -Wall -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L
cp -f vi /bin
I wonder whats causing this problem (I dont know C).
Kindly look into this. Thanks.
Do you want to put a License on this software or is it public domain?
I find snippets to be very convenient and I would like to have the possibility to define snippets in neatvi. I know, it's rather a feature than a customization.
At the moment I use snippets in vim but without using plugins. So I think it would be possible to have snippets in neatvi. But I need the map feature from vi. I have the following in my vimrc
for example:
inoremap ,dmath \begin{displaymath}<Enter>\end{displaymath}<Esc>O
I bind ,dmath
to
\begin{displaymath}
\end{displaymath}
After the <Esc>
key at the end, I use the command O
to open a line above \end{displaymath}
so my cursor is at the right place to write Latex code.
It's even possible to define some placeholders, for example:
inoremap ,fr \frac{}{<++>}<++><Esc>Fcla
In this case I want to insert \frac{}{}
. After writing ,fr
in insert mode, \frac{}{<++>}<++>
is inserted and the cursor is in the first curly brace. Then I have to define a shortcut to jump to the next <++>
. Perhaps it's not so powerful with some other snippets plugins, but it's enough for me and without the need to install a lot of dependencies.
To use it, I rely on map!
which is availabe in traditionnal vi. I did some tests, but it seems that the commands map
and map!
don't exist. Another problem, I defined the snippets in the vimrc
and if I understand right, there is no configuration file, only the config.h
. For me it would be no problem to write my snippet directly in the config.h
.
For more information and to see some animated examples: https://www.tomchaplin.xyz/blog/2019_02_10/Vim-for-LaTeX/ (go directly to: "placeholders").
Would be something like this possible ? Perhaps it's not even necessary to have the map
feature, but the possibility to write some code in the config.h
.
MorphOS says
In file included from vi.c:39:
regex.c:263:5: error: conflicting types for 're_comp'
263 | int re_comp(rcode *prog, const char *re, int nsubs, int flags)
| ^~~~~~~
In file included from vi.c:27:
/gg/include/unistd.h:144:10: note: previous declaration of 're_comp' was here
144 | char *re_comp __P((const char *));
| ^~~~~~~
vi.c:2047:14: fatal error: use of undeclared identifier 'SIGWINCH'
sigaction(SIGWINCH, &sa, NULL))
^
Hello,
I hope you're doing well.
First of all, I want to express my appreciation for this wonderful project and the tremendous effort you've put into it.
I'm currently torn between Neatvi and Nextvi, but I'm leaning towards Nextvi due to its HTML syntax highlighting patterns and some useful add-ons that have been integrated. However, I've encountered a real issue - the inability to edit files through links in the texts. Is this feature available but hidden, or is it simply not supported in Nextvi?
Best regards,
Leith
What about -O2
?
You may forget CFLAGS easily like I did for
http://aminet.net/package/text/edit/nextvi
/usr/bin/cc vi.c -pedantic -Wall -Wextra -Wno-implicit-fallthrough -Wno-missing-field-initializers -Wno-unused-parameter -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L -D_DARWIN_C_SOURCE -o vi
In file included from vi.c:34:
./vi.h:191:18: warning: a function declaration without a prototype is deprecated in all versions of C [-Wstrict-prototypes]
void syn_reloadft();
^
void
In file included from vi.c:40:
./ren.c:352:18: warning: a function declaration without a prototype is deprecated in all versions of C [-Wstrict-prototypes]
void syn_reloadft()
^
void
vi.c:200:25: warning: a function declaration without a prototype is deprecated in all versions of C [-Wstrict-prototypes]
static void vi_drawagain()
^
void
vi.c:589:24: warning: a function declaration without a prototype is deprecated in all versions of C [-Wstrict-prototypes]
static void vi_regprint()
^
void
vi.c:2038:23: warning: a function declaration without a prototype is deprecated in all versions of C [-Wstrict-prototypes]
static void sighandler()
^
void
5 warnings generated.
echo 'foo | bar' > file1; echo 'foo/bar' > file2;
vi
:edit +1 | s/|/PIPE/ | w file1 | e file2 | 1 | s/\//SLASH/ | wq
See https://pubs.opengroup.org/onlinepubs/9699919799/utilities/ex.html#tag_20_40_18_08
In ex_init() in ex.c, a backslash is added before spaces, % and #.
I have removed it as it prevents me from editing or viewing files containing these characters.
I have not encountered any issues so far.
Is there any particular purpose for doing this? It seems quite useless to me.
Around 6 months ago I noticed the issue with this patch, somehow it was refusing to find something that was clearly there. I back checked everything and figured it was only related to that patch. I don't remember exactly how to reproduce it, and I am not sure if the issue propagated to rstr.patch or not (likely not since I never bothered). I will run it to see if I can find the right combination of search kwd and text. It was consistent (ie not related to threading itself) as I recall.
Tab auto completion hangs in zsh, I've never read a zsh completion file before, but it looks like its running vi --version
to figure out if it's vim or not. Would probably be fixed by adding a --version
page, or by exiting if not running interactively, since it seems to just fallback to only auto completing file paths if its not vim.
if only - is specified, an additional empty buffer will be opened
if - and a file are specified, - will inherent the name of the last file
I tested if it was a result of the recent command line changes, since I saw similar issues when testing those, but checking out 6d98b26 and using 3 day old stdin_pipe patch had the same issue
/usr/bin/cc vi.c -pedantic -Wall -Wextra -Wno-implicit-fallthrough -Wno-missing-field-initializers -Wno-unused-parameter -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L -o vi
vi.c:2049:14: fatal error: use of undeclared identifier 'SIGWINCH'
sigaction(SIGWINCH, &sa, NULL))
^
1 error generated.
Darwin mbp 21.5.0 Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:29 PDT 2022; root:xnu-8020.121.3~4/RELEASE_ARM64_T8101 arm64
#if (!defined(_POSIX_C_SOURCE) || defined(_DARWIN_C_SOURCE))
#define SIGWINCH 28 /* window size changes */
#define SIGINFO 29 /* information request */
#endif
[33161.133236] vi[4489]: segfault (11) at 726f6772 nip 100082a4 lr 1001d930 code 1 in vi[10000000+30000]
[33161.133324] vi[4489]: code: 83ebfffc 7d615b78 4e800020 9421ffe0 93e1001c 7c3f0b78 907f0008 909f000c
[33161.133339] vi[4489]: code: 813f000c 2c090000 41800034 813f0008 <8129010c> 815f000c 7c0a4800 40800020
a segfault also happens when i built for iOS 5 but I didn't make an issue since it's a slightly more obscure platform, unsure if its the same issue
I very often execute a command on the file in the current buffer with
:! cmd %
where cmd
is my command. It worked fine until commit ced7ccd
and it seems since commit d11fbae
% is not replaced anymore with the filename in the current buffer. Perhaps there is something wrong the following function.
Or is it stored in another variable now ?
Hi,
With the addition of the exclamation mark and equal in regex, it should be possible to highlight multiline docstrings. I have been experimenting and have not succeeded.
Has anyone done this? Does anyone have suggestions?
I thought this might work (simple case with double quotes only), but it does not.
{"py", "\"\"\"[!\"\"\"]*?\"\"\"", {2 | SYN_IT}},
I am using this as a stop-gap measure.
{"py", "^[ \t]*\"\"\".*$", {2 | SYN_BD | SYN_RV}},
Thanks.
Is it possible to enable support for UTF-8 characters?
Also when I enter ctrl+v
to show tabs and spaces, in the source code I changed the >
symbol to »
, but it only shows ▯
. How can I fix that?
Thanks,
Julio
cat vi.c | ./vi -
no highlighting
MacOS has only had clock_gettime
since 10.12 sierra ~2016
Hello,
sometimes I need to insert some tabs, not spaces, really some tabs. As far as I know, to insert some tabs I need to do the following:
Ctrl+V Tab
Unfortunately, I get a Segmentation fault
.
Steps to reproduce:
nextvi
i
to enter the insert modeThen I get a Segmentation fault
The shortcut "Ctrl+V" in normal mode seems to work fine. I had to insert some tabs in the past and it worked without problem.
I have tested with the latest git version. Do you get the same ?
Making relases would be useful for packaging. I understand for a small/mature project it could be cumbersome, but it doesn't have to be more than snapshots' handles, with a monotonic nature, that's all.
How about also supporting "*" as key?
/usr/bin/cc vi.c -o vi -pedantic -Wall -Wextra -Wno-implicit-fallthrough -Wno-missing-field-initializers -Wno-unused-parameter -Wfatal-errors -std=c99 -D_POSIX_C_SOURCE=200809L -O2 -D_DARWIN_C_SOURCE
In file included from vi.c:38:
./led.c:371:20: warning: a function declaration without a prototype is deprecated in all versions of C [-Wstrict-prototypes]
static int get_time()
^
void
1 warning generated.
currently opening a file with CRLF line endings displays a garbage character at the end of each line
I was using Neovim user for a long. and I was using LSP for getting a lot of information about the codebase that I'm working on. like, jump to the definition of methods,...
Then I realized that LSP is bloated for me and tags are enough. and I really like the simplicity of tags in comparison to LSP.
so with ctags, I can start creating tags for my project, and with :tag
i can jump between functions.
I couldn't find tags in nextvi. It doesn't support it?
If not, what is the alternative?
Hello,
As written in the README, it's possible to get help in hund
with ?
. Does it work for you ? For me it doesn't work. I need to look at the source code if I want to know the shortcuts in hund
.
I can give the following information:
in vi
the command
:cm
returns :en
, so it should be the english keyboard. But I'm using the keyboard defined in Xorg.
hund
, when I want to run an ex command, I write :
and then the key ?
match the definition in Xorg. It's the same behavior as for other applications.?
doesn't work.h
,j
,k
,l
or Tab
.Did I miss something ?
Hi,
I'm a long term neovim user and I want to switch to a More minimal alternative that I can read/understand it's code base and change it based on my needs.
Untill I find nextvi.
I think the only thing that I will miss from neovim is code Intellisense via LSP.
Im not sure how you guys solved this issue in your daily programming.
I'm curious to know do you use extra tools like ctags? Or you don't use intelisence at all?
And what are yours reasons. Is it more efficient?
If I want to add Intellisense, where should I start? Or is it better to use external alternatives like ctags?
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.