aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
| * build(release.sh): regenerate docs after changing NVIM_API_PRERELEASE (#28229)zeertzjq2024-04-08
| | | | | | | | After #25574, the value of NVIM_API_PRERELEASE can affect docs, so docs need to be regenerated after changing NVIM_API_PRERELEASE.
| * build: add function add_targetdundargoc2024-04-08
| | | | | | | | | | | | | | It's a combination of add_custom_target and add_custom_command that does what most users probably expect should happen. This also fixes `make clean` removing files tracked by git.
| * vim-patch:9.1.0272: autocmd may change cwd after :tcd and :lcd (#28223)zeertzjq2024-04-08
| | | | | | | | | | | | | | | | | | Problem: Autocommand may change currect directory after :tcd and :lcd. Solution: Also clear tp_localdir and w_localdir when using aucmd_win. (zeertzjq) closes: vim/vim#14435 https://github.com/vim/vim/commit/9d956ee8eab64a0d412b045305fde5bc03d95d4a
| * vim-patch:9cd9e759ab1e (#28224)zeertzjq2024-04-08
| | | | | | | | | | | | | | | | | | | | | | | | runtime(doc): Normalise builtin-function optional parameter formatting These should generally be formatted as func([{arg}]) and referenced as {arg} in the description. closes: vim/vim#14438 https://github.com/vim/vim/commit/9cd9e759ab1e6e6adb24a23648eed41e4d94d522 Co-authored-by: Doug Kearns <dougkearns@gmail.com>
| * docs: don't mention executable() can return -1dundargoc2024-04-06
| | | | | | | | This cannot happen for neovim.
| * revert: "vim-patch:9.1.0055: formatting long lines is slow"zeertzjq2024-04-06
| | | | | | | | | | | | | | Revert "vim-patch:9.1.0055: formatting long lines is slow (#27199)" This reverts commit 89a9745a1a55dc9ffd0f8292735e45bae6c7b01e. Fix #28197
| * fix: adjust error message for error in UI event callback (#28200)zeertzjq2024-04-06
| | | | | | | | | | | | Also close Nvim instance before removing log file, otherwise the Nvim instance will still write to the log file. Also adjust log level in libuv_process_spawn(). Ref #27660
| * version.c: update [skip ci] (#28201)github-actions[bot]2024-04-06
| | | | | | Co-authored-by: marvim <marvim@users.noreply.github.com>
| * fix(column): ignore empty signcols range (#28177)luukvbaal2024-04-06
| | | | | | | | | | | | | | | | Problem: Invalid assert for empty signcols range. The empty range should already be removed from "b_signcols" at this point. The "clear" == kTrue call before the splice that made the range empty will have removed it, and the "clear" == kNone call after the splice already ignores the empty range. Solution: Return early when "row2" < "row1".
| * vim-patch:9.1.0267: File name entered in GUI dialog is ignoredzeertzjq2024-04-06
| | | | | | | | | | | | | | | | | | | | Problem: File name entered in GUI dialog is ignored (after v9.1.0265) Solution: Only set file name to "Untitled" if GUI dialog didn't set it. (zeertzjq) closes: vim/vim#14417 https://github.com/vim/vim/commit/c20bdf1107d48a1c14713709d12d429e761132af
| * vim-patch:9.1.0265: console dialog cannot save unnamed buffers (#28185)zeertzjq2024-04-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: console dialog cannot save unnamed buffers Solution: set bufname before save (glepnir). Define dialog_con_gui to test for GUI+Console dialog support, use it to skip the test when the GUI feature has been defined. Note: The dialog_changed() function will also try to call the browse_save_fname() function, when FEAT_BROWSE is defined (which is only defined in a GUI build of Vim). This will eventually lead to a call of do_browse(), which causes an error message if a GUI is not currently running (see the TODO: in do_browse()) and will then lead to a failure in Test_goto_buf_with_onfirm(). Therefore, we must disable the Test_goto_buf_with_onfirm(), when the dialog_con_gui feature is enabled (which basically means dialog feature for GUI and Console builds, in contrast to the dialog_con and dialog_gui feature). (Previously this wasn't a problem, because the test aborted in the YES case for the :confirm :b XgotoConf case and did therefore not run into the browse function call) closes: vim/vim#14398 https://github.com/vim/vim/commit/df46115fc839c8912ed60646e86a412e5180ba1d Co-authored-by: glepnir <glephunter@gmail.com>
| * vim-patch:8.1.0815: dialog for file changed outside of Vim not tested (#28184)zeertzjq2024-04-05
| | | | | | | | | | | | | | | | | | Problem: Dialog for file changed outside of Vim not tested. Solution: Add a test. Move FileChangedShell test. Add 'L' flag to feedkeys(). https://github.com/vim/vim/commit/5e66b42aae7c67a3ef67617d4bd43052ac2b73ce Co-authored-by: Bram Moolenaar <Bram@vim.org>
| * build: fix link error for `_BitScanForward64` (#28173)Famiu Haque2024-04-05
| | | | | | | | Problem: The usage of `_BitScanForward64` causes linking to fail on some systems. Solution: Correctly check if it exists using `check_c_source_compiles`.
| * vim-patch:9.1.0259: Normal mode TextChanged isn't tested properly (#28167)zeertzjq2024-04-04
| | | | | | | | | | | | | | | | | | | | Problem: Normal mode TextChanged isn't tested properly. Solution: Combine Test_Changed_ChangedI() and Test_Changed_ChangedI_2() and also run it on Windows. Fix a typo in main.c. (zeertzjq) closes: vim/vim#14396 https://github.com/vim/vim/commit/c422662933275484e61af79d8148898337a5c38e
| * fix(stdpath): remove duplicate directories (#26653)Raphael2024-04-03
| |
| * Merge pull request #28157 from fredizzimo/fsundvik/fix-iobfredl2024-04-03
| |\ | | | | | | fix: prevent child processes from inheriting ui channel file descriptors
| | * fix: prevent child processes from inheriting ui channel file descriptorsFred Sundvik2024-04-02
| | |
| * | vim-patch:8.2.4098: typing "interrupt" at debug prompt may keep exception ↵zeertzjq2024-04-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | around (#28161) Problem: Typing "interrupt" at debug prompt may keep exception around, causing function calls to fail. Solution: Discard any exception at the toplevel. (closes vim/vim#9532) https://github.com/vim/vim/commit/069613c9e8645acea3a128c15ebdbf56e2219d44 Co-authored-by: Bram Moolenaar <Bram@vim.org>
| * | vim-patch:9.1.0254: [security]: Heap buffer overflow when calling ↵zeertzjq2024-04-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | complete_add() in 'cfu' Problem: [security]: Heap buffer overflow when calling complete_add() in the first call of 'completefunc' Solution: Call check_cursor() after calling 'completefunc' (zeertzjq) closes: vim/vim#14391 https://github.com/vim/vim/commit/0a419e07a705675ac159218f42c1daa151d2ceea
| * | vim-patch:9.0.0581: adding a character for incsearch fails at end of linezeertzjq2024-04-03
| |/ | | | | | | | | | | | | | | | | Problem: Adding a character for incsearch fails at end of line. Solution: Only check cursor line number. https://github.com/vim/vim/commit/d4566c14e71c55dcef05fb34ea94eba835831527 Co-authored-by: Bram Moolenaar <Bram@vim.org>
| * test: silence expected errorsdundargoc2024-04-02
| | | | | | | | This will remove unrelated errors in .nvimlog at the end of test output.
| * refactor: informative error msg for 'noautocmd' (#28147)Will Hopkins2024-04-02
| | | | | | | | | | Problem: Attempting to set 'noautocmd' for an existing window throws an error that just says "Invalid key: 'noautocmd'" which is not very helpful. Solution: Explain that 'noautocmd' can't be used with existing windows.
| * vim-patch:9.1.0251: Filetype test fails (#28142)zeertzjq2024-04-01
| | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Filetype test fails. Solution: Move detection by name before detection by extension. Improve TextChanged test and remove wrong test and fix a typo in a comment (zeertzjq). closes: vim/vim#14373 https://github.com/vim/vim/commit/8eb7523802cb51984e2202d08a4fbc1a2cd803c7 The changes to filetype.vim are N/A since Nvim always prefers filename matches to extension matches.
| * Merge pull request #28080 from echasnovski/intro-buf-changezeertzjq2024-04-01
| |\ | | | | | | fix(intro): link showing intro to state at start
| | * fix(intro): clear intro if new buffer is shown in focused floatEvgeni Chasnovski2024-03-29
| | |
| | * fix(intro): link showing intro to state at startEvgeni Chasnovski2024-03-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Current behavior of stateful intro message is too persistent. For example, it is still drawn if new empty buffer is shown in current window (either by explicitly setting it or after `tabnew`). Although the buffer is empty, the act of it being shown should be made visible. Solution: Make intro message persist if all is true: - Current buffer is the same as it was just after start, i.e. empty nameless with initial handle (i.e. 1). - Current window is the same as it was just after start, i.e. single non-floating with initial handle.
| * | vim-patch:9.1.0231: Filetype may be undetected when SwapExists sets ft in ↵zeertzjq2024-04-01
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | other buf (#28136) Problem: Filetype may be undetected when a SwapExists autocommand sets filetype in another buffer. Solution: Make filetype detection state buffer-specific. Also fix a similar problem for 'modified' (zeertzjq). closes: vim/vim#14344 https://github.com/vim/vim/commit/5bf6c2117fcef85fcf046c098dd3eb72a0147859
| * | vim-patch:9.1.0230: TextChanged autocommand not triggered under some ↵zeertzjq2024-04-01
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | circumstances (#28135) Problem: TextChanged autocommand not triggered under some circumstances (Sergey Vlasov) Solution: Trigger TextChanged when TextChangedI has not been triggered fixes: vim/vim#14332 closes: vim/vim#14339 https://github.com/vim/vim/commit/86032702932995db74fed265ba99ae0c823cb75d Co-authored-by: Christian Brabandt <cb@256bit.org>
| * | fix(api): set script context when using nvim_set_hl (#28123)zeertzjq2024-03-31
| | |
| * | feat(lua): pass keys before mapping to vim.on_key() callback (#28098)zeertzjq2024-03-31
| | | | | | | | | Keys before mapping (i.e. typed keys) are passed as the second argument.
| * | Merge pull request #28114 from echasnovski/builtin-hl-grey-grayzeertzjq2024-03-30
| |\ \ | | | | | | | | fix(highlight): add `Nvim{Light,Dark}Gray{1,2,3,4}` colors
| | * | fix(highlight): consistently spell "Goldenrod"Evgeni Chasnovski2024-03-30
| | | |
| | * | fix(highlight): add `Nvim{Light,Dark}Gray{1,2,3,4}` colorsEvgeni Chasnovski2024-03-30
| | | |
| * | | fix: explain that user should run nvim with -V1 to see more informationdundargoc2024-03-30
| |/ / | | | | | | | | | | | | It's not obvious for users how to figure out where a mapping is set from only "Last set from Lua".
| * | test: use matches(...) instead of ok(string.find(...)) (#28111)zeertzjq2024-03-30
| | |
| * | fix(extmarks): splice earlier when opening new line (#28108)zeertzjq2024-03-30
| | | | | | | | | | | | Related #26364 #26499 #26501 Fix #28107
| * | fix(terminal): fix duplicate recording with mouse click (#28103)zeertzjq2024-03-29
| | |
| * | test: add a bit more testing for vim.on_key() (#28095)zeertzjq2024-03-29
| | | | | | | | | | | | | | | Also: - Don't use NUMBUFLEN as buffer length as its unrelated. - Restore accidentally removed comment from last commit.
| * | vim-patch:9.1.0227: Recording may still be wrong in Select mode (#28092)zeertzjq2024-03-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Recording may still be wrong in Select mode (after 8.2.3993). Solution: Make sure a character isn't split between two buffer blocks. (zeertzjq) closes: vim/vim#14326 https://github.com/vim/vim/commit/ea95f1a5ad2455c7fd1eee2413ac7a3460ef4f8a
| * | vim-patch:9.1.0228: Two unrelated things are tested by a single test (#28093)zeertzjq2024-03-29
| |/ | | | | | | | | | | | | | | | | | | Problem: Two unrelated things are tested by a single test. Solution: Split it into two, restoring the old Test_brace_single_line(). Add missing cleanup to some tests. (zeertzjq) closes: vim/vim#14323 https://github.com/vim/vim/commit/ad493ef3ea9ef7f2b0badcd2298883b5ab6e4ef4
| * feat(ui): indicate margins for the area used by win_viewportbfredl2024-03-29
| | | | | | | | | | | | | | | | Problem: using win_viewport for implementing smooth scrolling in an external UI might run into problems when winbar or borders is used, as there is no indication that the entire grid is not used for scrolled buffer text. Solution: add `win_viewport_margins` event.
| * test: skip another flaky test on macOS (#28087)zeertzjq2024-03-29
| |
| * fix(tui): don't use DECRQSS in screen or tmux (#28086)zeertzjq2024-03-29
| | | | | | They behave strangely when receiving that.
| * Merge pull request #28044 from luukvbaal/vim-9.1.0211zeertzjq2024-03-28
| |\ | | | | | | vim-patch:9.1.{0211,0215}
| | * vim-patch:9.1.0215: Half-page scrolling does not support smooth-scrollingLuuk van Baal2024-03-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Page-wise scrolling with Ctrl-D/Ctrl-U implements it's own logic to change the topline and cursor. More logic than necessary for scrolling with Ctrl-F/Ctrl-B was removed in patch 9.1.0211. Solution: Re-use the logic from Ctrl-E/Ctrl-Y/Ctrl-F/Ctrl-B while staying backward compatible as much as possible. Restore some of the logic that determined how many lines will be scrolled (Luuk van Baal) https://github.com/vim/vim/commit/5a2e3ec9ac72b6e644fea4ebba7e632498296e2f
| | * vim-patch:9.1.0211: page-wise scrolling does not support smooth-scrollingLuuk van Baal2024-03-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Page-wise scrolling with Ctrl-F/Ctrl-B implements it's own logic to change the topline and cursor. In doing so, skipcol is not handled properly for 'smoothscroll', and virtual lines. Solution: Re-use the logic from Ctrl-E/Ctrl-Y while staying backward compatible as much as possible. https://github.com/vim/vim/commit/b9f5b95b7bec2414a5a96010514702d99afea18e
| * | vim-patch:9.1.0220: Few typos in source and test files (#28076)zeertzjq2024-03-28
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Typos in code and tests. Solution: Fix typos (zeertzjq). closes: vim/vim#14321 https://github.com/vim/vim/commit/c029c131ea7822514d67edb9be2de76d076aa267
| * | vim-patch:9.1.0218: Unnecessary multiplications in backspace code (#28075)zeertzjq2024-03-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Unnecessary multiplications in backspace code, as "col / ts * ts" is the same as "col - col % ts". Solution: Change "col / ts * ts" to "col - col % ts". Adjust the loop and the comments ins_bs() to be easier to understand. Update tests to reset 'smarttab' properly. (zeertzjq) closes: vim/vim#14308 https://github.com/vim/vim/commit/8ede7a069419e0e01368c65a2d0c79d6332aa6cd
| * | vim-patch:9.1.0217: regexp: verymagic cannot match before/after a mark (#28074)zeertzjq2024-03-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: regexp: verymagic cannot match before/after a mark Solution: Correctly check for the very magic check (Julio B) Fix regexp parser for \v%>'m and \v%<'m Currently \v%'m works fine, but it is unable to match before or after the position of mark m. closes: vim/vim#14309 https://github.com/vim/vim/commit/46fa3c7e271eb2abb05a0d9e6dbc9c36c2b2da02 Co-authored-by: Julio B <julio.bacel@gmail.com>
| * | vim-patch:9.1.0214: Duplicate condition in win_lbr_chartabsize() (#28072)zeertzjq2024-03-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Duplicate condition in win_lbr_chartabsize(). Solution: Remove the duplicate condition, as it's already checked above. (zeertzjq) closes: vim/vim#14320 https://github.com/vim/vim/commit/5532d3b3f0c73d4e0fa07122ebbed3bf201870f9
generated by cgit (git 2.34.1) at 2025-05-03 07:56:21 +0000