aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
| * | vim-patch:9.0.1213: adding a line below the last one does not expand fold ↵zeertzjq2023-01-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (#21869) Problem: Adding a line below the last one does not expand fold. Solution: Do not skip mark_adjust() when adding lines below the last one. (Brandon Simmons, closes vim/vim#11832, closes vim/vim#10698) https://github.com/vim/vim/commit/da3dd7d857ba4fb4bf408dedd1d9d6a2d5e2ae9f Co-authored-by: Brandon Simmons <simmsbra@gmail.com>
| * | refactor(PVS/V1048): remove unnecessary assignment (#21870)Lucas Merritt2023-01-18
| | |
| * | Merge pull request #21868 from zeertzjq/vim-9.0.1214zeertzjq2023-01-18
| |\ \ | | | | | | | | vim-patch:9.0.{1214,1215}
| | * | vim-patch:9.0.1215: using isalpha() adds dependency on current localezeertzjq2023-01-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Using isalpha() adds dependency on current locale. Solution: Do not use isalpha() for recognizing a URL or the end of an Ex command. (closes vim/vim#11835) https://github.com/vim/vim/commit/0ef9a5c09482649cf0cc6768ed6fc640b4ed2a0a
| | * | vim-patch:9.0.1214: file left behind after running testszeertzjq2023-01-18
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | Problem: File left behind after running tests. Solution: Delete the file. (Dominique Pellé, closes vim/vim#11839) https://github.com/vim/vim/commit/541c87c808df91b55e51fedc4987152a3edfe80d Co-authored-by: Dominique Pelle <dominique.pelle@gmail.com>
| * / vim-patch:9.0.1212: cannot read back what setcellwidths() has done (#21867)zeertzjq2023-01-18
| |/ | | | | | | | | | | | | | | Problem: Cannot read back what setcellwidths() has done. Solution: Add getcellwidths(). (Kota Kato, closes vim/vim#11837) https://github.com/vim/vim/commit/66bb9ae70f7371456ed76518076d2a344f8ab417 Co-authored-by: Kota Kato <github@kat0h.com>
| * fix(treesitter): really restore syntaxLewis Russell2023-01-17
| | | | | | | | | | - also unset b:ts_highlight on stop() Fixes: #21836
| * refactor: replace char_u with char 22 (#21786)dundargoc2023-01-17
| | | | | | Work on https://github.com/neovim/neovim/issues/459
| * Merge pull request #21859 from zeertzjq/vim-8.2.4617zeertzjq2023-01-17
| |\ | | | | | | vim-patch:8.2.{4617,4618,4620,5126}
| | * vim-patch:8.2.5126: substitute may overrun destination bufferzeertzjq2023-01-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Substitute may overrun destination buffer. Solution: Disallow switching buffers in a substitute expression. https://github.com/vim/vim/commit/d6211a52ab9f53b82f884561ed43d2fe4d24ff7d Co-authored-by: Bram Moolenaar <Bram@vim.org>
| | * vim-patch:8.2.4618: cmdline completion does not recognize single letter commandszeertzjq2023-01-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Command line completion does not recognize single letter commands. Solution: Use the condition from find_ex_command(). https://github.com/vim/vim/commit/f4f0525c34d2aa32f214155b0dadcd274ed05dd1 vim-patch:8.2.4620: two letter substitute commands don't work Problem: Two letter substitute commands don't work. (Yegappan Lakshmanan) Solution: Invert condition. https://github.com/vim/vim/commit/1e2c4175dce903986dac66ba9326ae562b159421 Co-authored-by: Bram Moolenaar <Bram@vim.org>
| | * vim-patch:8.2.4617: no completion for :scriptnameszeertzjq2023-01-17
| |/ | | | | | | | | | | | | | | | | | | Problem: No completion for :scriptnames. Solution: Implement :scriptnames completion. (Yegappan Lakshmanan, closes vim/vim#10005) https://github.com/vim/vim/commit/454ce6737cadb82886f1fc0eb9e8666cc59ae42b Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
| * build(deps): bump tree-sitter to HEAD - eb970a83a (#21858)Christian Clason2023-01-17
| | | | | | includes https://github.com/tree-sitter/tree-sitter/commit/efd22e452be528b091a8b691e38b65d43dc6f0ff which fixes some errors around infinite loops with injections
| * vim-patch:8.2.4483: command completion makes two rounds to collect matches ↵zeertzjq2023-01-17
| | | | | | | | | | | | | | | | | | | | | | (#21857) Problem: Command completion makes two rounds to collect matches. Solution: Use a growarray to collect matches. (Yegappan Lakshmanan, closes vim/vim#9860) https://github.com/vim/vim/commit/5de4c4372d4366bc85cb66efb3e373439b9471c5 Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
| * vim-patch:8.2.4959: using NULL regexp program (#21855)zeertzjq2023-01-17
| | | | | | | | | | | | | | | | Problem: Using NULL regexp program. Solution: Check for regexp program becoming NULL in more places. https://github.com/vim/vim/commit/b62dc5e7825bc195efe3041d5b3a9f1528359e1c Co-authored-by: Bram Moolenaar <Bram@vim.org>
| * vim-patch:8.2.4928: various white space and cosmetic mistakes (#21854)zeertzjq2023-01-17
| | | | | | | | | | | | | | | | Problem: Various white space and cosmetic mistakes. Solution: Change spaces to tabs, improve comments. https://github.com/vim/vim/commit/6ed545e79735f23ff8e650bc2f0967e5a0baedc9 Co-authored-by: Bram Moolenaar <Bram@vim.org>
| * vim-patch:8.2.4917: fuzzy expansion of option names is not right (#21853)zeertzjq2023-01-17
| | | | | | | | | | | | | | | | | | Problem: Fuzzy expansion of option names is not right. Solution: Pass the fuzzy flag down the call chain. (Christian Brabandt, closes vim/vim#10380, closes vim/vim#10318) https://github.com/vim/vim/commit/cb747899bd99361a299a163f3aa55d5fe7d6f798 Co-authored-by: Christian Brabandt <cb@256bit.org>
| * vim-patch:9.0.0089: fuzzy argument completion doesn't work for shell ↵zeertzjq2023-01-17
| | | | | | | | | | | | | | | | | | | | | | commands (#21852) Problem: Fuzzy argument completion doesn't work for shell commands. Solution: Check for cmdidx not being CMD_bang. (Yegappan Lakshmanan, closes vim/vim#10769) https://github.com/vim/vim/commit/7db3a8e3298bf7c7c3f74cc9c1add04f29e78d2d Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
| * Merge pull request #21851 from zeertzjq/vim-8.2.4482zeertzjq2023-01-17
| |\ | | | | | | vim-patch:8.2.{4482,4485}: fuzzy cmdline custom completion
| | * fix(completion): correct what modes support fuzzy completionzeertzjq2023-01-17
| | |
| | * vim-patch:8.2.4482: no fuzzy cmdline completion for user defined completionzeertzjq2023-01-17
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: No fuzzy cmdline completion for user defined completion. Solution: Add fuzzy completion for user defined completion. (Yegappan Lakshmanan, closes vim/vim#9858) https://github.com/vim/vim/commit/afd4ae35d66b2e7732eceb5ad9f6b4ece6b7c64c Cherry-pick related docs from Vim runtime. N/A patches for version.c: vim-patch:8.2.4485: compiler warning for uninitialized variable vim-patch:8.2.4732: duplicate code to free fuzzy matches Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
| * Merge pull request #21850 from zeertzjq/vim-8.2.4463zeertzjq2023-01-17
| |\ | | | | | | vim-patch:8.2.{4463,4465,4475,4477,4478,4479,4608}: fuzzy cmdline builtin completion
| | * vim-patch:8.2.4608: getcompletion() does not work when 'wildoptions' has "fuzzy"zeertzjq2023-01-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: getcompletion() does not work properly when 'wildoptions contains "fuzzy". Solution: Do not use addstar(). (Yegappan Lakshmanan, closes vim/vim#9992, closes vim/vim#9986) https://github.com/vim/vim/commit/e7dd0fa2c61fe71f12c72b0dcb7bb6415eb048fb Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
| | * vim-patch:8.2.4479: no fuzzy completieon for maps and abbreviationszeertzjq2023-01-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: No fuzzy completieon for maps and abbreviations. Solution: Fuzzy complete maps and abbreviations. (Yegappan Lakshmanan, closes vim/vim#9856) https://github.com/vim/vim/commit/6caeda2fce4bccac2dd43ca9fee1d32ee96b708d Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
| | * vim-patch:8.2.4478: crash when using fuzzy completionzeertzjq2023-01-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Crash when using fuzzy completion. Solution: Temporary fix: put back regexp. (closes vim/vim#9852, closes vim/vim#9851) https://github.com/vim/vim/commit/00333cb3b341499df8729b9345f0bbad968cda0b Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
| | * vim-patch:8.2.4477: crash when using fuzzy completionzeertzjq2023-01-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Crash when using fuzzy completion. Solution: Temporary fix: put back regexp. (closes vim/vim#9851) https://github.com/vim/vim/commit/29ab6ce9f36660cffaad3c8789e71162e5db5d2f Co-authored-by: Bram Moolenaar <Bram@vim.org>
| | * vim-patch:8.2.4475: fuzzy cmdline completion does not work for lower casezeertzjq2023-01-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Fuzzy cmdline completion does not work for lower case. Solution: Also use fuzzy completion for lower case input. (Yegappan Lakshmanan, closes vim/vim#9849) https://github.com/vim/vim/commit/4df5b33f206210fec2a0297aea27e7db8b5173c0 Initialize "regmatch" to avoid using uninitialized memory. Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
| | * vim-patch:8.2.4465: fuzzy completion does not order matches properlySean Dewar2023-01-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Fuzzy completion does not order matches properly. Solution: Do not use regular expression match. (Yegappan Lakshmanan, closes vim/vim#9843) https://github.com/vim/vim/commit/5ec633b9b0400519db60253cb5846e50394218b4 Nvim's ExpandGeneric() was refactored to eliminate looping for "round", so the patch has been adapted. fuzzy_match_str() change was already applied earlier. In Test_wildoptions_fuzzy(), test for NvimParenthesis over MatchParen for :syntax list, as the fuzzy matching algorithm prefers the former (even in Vim). Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
| | * vim-patch:8.2.4463: completion only uses strict matchingSean Dewar2023-01-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Completion only uses strict matching. Solution: Add the "fuzzy" item for 'wildoptions'. (Yegappan Lakshmanan, closes vim/vim#9803) https://github.com/vim/vim/commit/38b85cb4d7216705058708bacbc25ab90cd61595 Use MAX_FUZZY_MATCHES in fuzzy_match_str(). Omit fuzmatch_str_free() as it is only used on allocation failure. Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
| | * refactor: remove char_u from arguments of fuzzy_match()zeertzjq2023-01-17
| |/ | | | | | | Also change some single quotes to double quotes.
| * fix(tabline): avoid memory leak in tabline click definitions (#21847)luukvbaal2023-01-17
| | | | | | | | | | | | Problem: Memory is leaked in tabline click definitions since https://github.com/neovim/neovim/pull/21008. Solution: Add back a call to `stl_clear_click_defs()` that was lost in the refactor PR.
| * fix: failing XDG test on Windows CIJustin M. Keyes2023-01-17
| | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Failing Windows CI: FAILED test/functional\options\defaults_spec.lua @ 361: XDG defaults with too long XDG variables are correctly set test\helpers.lua:134: Pattern "Failed to start server: no such file or directory: /X/X/X" not found in log (last 10 lines): Xtest-defaults-log: FAILED test/functional\options\defaults_spec.lua @ 435: XDG defaults with XDG variables that can be expanded are not expanded test\helpers.lua:134: Pattern "Failed to start server: no such file or directory: %$XDG_RUNTIME_DIR%/" not found in log (last 10 lines): Xtest-defaults-log: Solution: The assert_log() statements are not relevant on Windows, because there XDG_RUNTIME_DIR is not used for creating servers, it uses \\.pipe\….
| * vim-patch:9.0.1208: code is indented more than necessary (#21846)zeertzjq2023-01-17
| | | | | | | | | | | | | | | | | | | | | | Problem: Code is indented more than necessary. Solution: Use an early return where it makes sense. (Yegappan Lakshmanan, closes vim/vim#11819) https://github.com/vim/vim/commit/a41e221935edab62672a15123af48f4f14ac1c7d Cherry-pick check_text_or_curbuf_locked() from patch 9.0.0947. Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
| * test(statuscolumn): %l should follow default wrap behavior (#21766)Brian Koropoff2023-01-17
| |
| * refactor: fix sign conversion warning from gcc (#21833)dundargoc2023-01-17
| |
| * Merge #21844 test: avoid noise in test logsJustin M. Keyes2023-01-16
| |\
| | * refactor(tests): lift retry() into assert_log()Justin M. Keyes2023-01-17
| | |
| | * test: avoid noise in NVIM_LOG_FILEJustin M. Keyes2023-01-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Tests that _intentionally_ fail certain conditions cause noise in $NVIM_LOG_FILE: $NVIM_LOG_FILE: /home/runner/work/neovim/neovim/build/.nvimlog (last 100 lines) WRN 2023-01-16T18:26:27.673 T599.7799.0 unsubscribe:519: RPC: ch 1: tried to unsubscribe unknown event 'doesnotexist' WRN 2023-01-16T18:29:00.557 ?.11151 server_start:163: Failed to start server: no such file or directory: /X/X/X/... WRN 2023-01-16T18:33:07.269 127.0.0.1:12345 server_start:163: Failed to start server: address already in use: 127.0.0.1 ... -- Output to stderr: module 'vim.shared' not found: no field package.preload['vim.shared'] no file './vim/shared.lua' no file '/home/runner/nvim-deps/usr/share/lua/5.1/vim/shared.lua' no file '/home/runner/nvim-deps/usr/share/lua/5.1/vim/shared/init.lua' no file '/home/runner/nvim-deps/usr/lib/lua/5.1/vim/shared.lua' no file '/home/runner/nvim-deps/usr/lib/lua/5.1/vim/shared/init.lua' no file './vim/shared.so' ... E970: Failed to initialize builtin lua modules Solution: - Log to a private $NVIM_LOG_FILE in tests that intentionally fail and cause ERR log messages. - Assert that the expected messages are actually logged.
| * | fix(api): avoid memory leak with click functions in nvim_eval_statusline() ↵luukvbaal2023-01-17
| |/ | | | | | | | | | | | | | | | | (#21845) Problem: Allocated click function memory is lost due to `nvim_eval_statusline()` not passing in a `StlClickRecord`. Solution: Do not allocate click function memory if `tabtab == NULL`. Resolve #21764, supersede #21842.
| * Merge pull request #21768 from luukvbaal/test-virtlinezeertzjq2023-01-17
| |\ | | | | | | | | | | | | | | | | | | | | | fix(column)!: ensure 'statuscolumn' works with virtual and wrapped lines BREAKING CHANGE: In 'statuscolumn' evaluation, `v:wrap` has been replaced by `v:virtnum`. `v:virtnum` is negative when drawing virtual lines, zero when drawing the actual buffer line, and positive when drawing the wrapped part of a buffer line.
| | * fix(column): avoid drawing columns for virt_lines_leftcolLuuk van Baal2023-01-16
| | | | | | | | | | | | | | | | | | | | | | | | Problem: The default fold column, as well as the 'statuscolumn', were drawn unnecessarily/unexpectedly for virtual lines placed with `virt_lines_leftcol` set. Solution: Skip the column states if a virtual line with `virt_lines_leftcol` set will be drawn.
| | * fix(column)!: ensure 'statuscolumn' works with virtual and wrapped linesLuuk van Baal2023-01-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: The `'statuscolumn'` was not re-evaluated for wrapped lines, when preceded by virtual/filler lines. There was also no way to distinguish virtual and wrapped lines in the status column. Solution: Make sure to rebuild the statuscolumn, and replace variable `v:wrap` with `v:virtnum`. `v:virtnum` is negative when drawing virtual lines, zero when drawing the actual buffer line, and positive when drawing the wrapped part of a buffer line.
| * | Merge pull request #21839 from seandewar/lua-health-fixSean Dewar2023-01-16
| |\ \ | | | | | | | | feat(health): detect tmux RGB support via `client_termfeatures`
| | * | feat(health): detect tmux RGB support via `client_termfeatures`Sean Dewar2023-01-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: On tmux v3.2+, the `terminal-features` option may be used to enable RGB capabilities over `terminal-overrides`. However, `show-messages` cannot be used to detect if RGB capabilities are enabled using `terminal-features`. Solution: Try to use `display-message -p #{client_termfeatures}` instead. The returned features include "RGB" if either "RGB" is set in `terminal-features`, or if "Tc" or "RGB" is set in `terminal-overrides` (as before). Nothing is returned by tmux versions older than v3.2, so fallback to checking `show-messages` in that case. Also, un-Vimscriptify the previous logic a bit, and change the error message to point to using the `terminal-features` option instead for newer tmux versions.
| | * | fix(health): fix `tmux_esc_time` comparisonSean Dewar2023-01-16
| | |/ | | | | | | | | | | | | | | | | | | Regression from the health.vim to .lua changes. Unlike Vim script, Lua does not implicitly convert strings to numbers, so this comparison threw an error.
| * | Merge pull request #21828 from clason/bump-libvtermChristian Clason2023-01-16
| |\ \ | | |/ | |/| build(deps): bump libvterm to v0.3.1
| | * build(deps): bump libvterm to v0.3.1Christian Clason2023-01-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Included patches: 821. By Paul "LeoNerd" Evans on 2022-12-29 Don't bother to emit the unrecognised sequence in DECRQSS response as it provides an echo roundtrip possibility 820. By Paul "LeoNerd" Evans on 2022-11-26 erase_internal() should only set fg/bg colour, resetting other attributes (especially RV) 819. By Paul "LeoNerd" Evans on 2022-11-09 Added vterm_screen_set_default_colors(), which repaints the cells in the buffer(s) 818. By Paul "LeoNerd" Evans on 2022-11-09 Permit either colour argument to be NULL to vterm_state_set_default_colors() 817. By Paul "LeoNerd" Evans on 2022-10-01 Delete the mk_wcswidth functions as they're not used; guard the CJK-wide one with an ifdef as by default we don't use it 816. By Paul "LeoNerd" Evans on 2022-10-01 Make sure to supply empty (void) prototype to functions that take no arguments in bin/vterm-ctrl.c
| * | docs: treesitter.add_directive, add_predicate #21206Ching Pei Yang2023-01-16
| | |
| * | build(deps): bump LuaJIT to HEAD - d0e88930dRaphael2023-01-16
| | | | | | | | | | | | | | | | | | build(deps): bump LuaJIT to HEAD-d0e88930d Don't fail for Clang builds, which pretend to be an ancient GCC. Fix compiler warning.
| * | Merge pull request #20945 from erw7/feat-more-exception-infozeertzjq2023-01-16
| |\ \ | | | | | | | | feat(api): show more exception info
generated by cgit (git 2.34.1) at 2025-06-25 10:34:32 +0000