aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* refactor(options)!: graduate shortmess+=f flagbfredl2023-09-23
| | | | | | | Not everything needs to be crazy overconfigurable. Also fixes a warning in latest clang which didn't approve of the funky math switch statement in append_arg_number
* fix(provider): cannot detect python3.12 #25316Jongwook Choi2023-09-23
| | | | | | | | | | | | | | | | | | | PROBLEM: The builtin python3 provider cannot auto-detect python3.12 when g:python3_host_prog is not set. As a result, when python3 on $PATH is currently python 3.12, neovim will fail to load python3 provider and result in `has("python3") == 0`, e.g., "Failed to load python3 host. You can try to see what happened by ..." ROOT CAUSE: the `system()` call from `provider#pythonx#DetectByModule` does not ignore python warnings, and `pkgutil.get_loader` will print a warning message in the very first line: ``` <string>:1: DeprecationWarning: 'pkgutil.get_loader' is deprecated and slated for removal in Python 3.14; use importlib.util.find_spec() instead ``` SOLUTION: - Use `importlib.util.find_spec` instead (python >= 3.4) - Use `-W ignore` option to prevent any potential warning messages
* build(deps): bump luajit to HEAD - 97c75843cChristian Clason2023-09-23
|
* fix(lua): show error message when failing to set variable (#25321)zeertzjq2023-09-23
|
* fix(unhide): close floating windows first (#25318)zeertzjq2023-09-23
|
* vim-patch:8.2.4609: :unhide does not check for failing to close a window ↵zeertzjq2023-09-23
| | | | | | | | | | | (#25317) Problem: :unhide does not check for failing to close a window. Solution: When closing a window fails continue with the next one. Do not try closing the autocmd window. (closes vim/vim#9984) https://github.com/vim/vim/commit/6f2465d336a9d4afe392db4084ef7e9db17e67c1 Co-authored-by: Bram Moolenaar <Bram@vim.org>
* fix(tui): make :cquit work properly with remote TUI (#25313)zeertzjq2023-09-23
|
* Merge pull request #25286 from rktjmp/doc-vim-schedule-wrapzeertzjq2023-09-23
|\ | | | | docs: add more context to vim.schedule_wrap
| * docs: update vim.schedule param name and typeOliver Marriott2023-09-23
| | | | | | | | | | Per https://github.com/neovim/neovim/pull/25286#discussion_r1332861721 and https://github.com/neovim/neovim/pull/25286#discussion_r1334318352
| * docs: clarify vim.schedule_wrap behaviourOliver Marriott2023-09-22
| | | | | | | | | | | | | | | | | | | | - Remove the usage of the term "defer" to avoid confusion with `vim.defer_fn`, which also calls `vim.schedule_wrap` internally. - Explicitly state that `vim.schedule_wrap` returns a function in the text. - Mention that arguments are passed along. - Include a usage example. - Rename param to `fn`.
* | fix(meta): include vim.jsonMaria José Solano2023-09-22
| |
* | fix(languagetree): don't treat unparsed nodes as occupying full rangeL Lllvvuu2023-09-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is incorrect in the following scenario: 1. The language tree is Lua > Vim > Lua. 2. An edit simultaneously wipes out the `_regions` of all nodes, while taking the Vim injection off-screen. 3. The Vim injection is not re-parsed, so the child Lua `_regions` is still `nil`. 4. The child Lua is assumed, incorrectly, to occupy the whole document. 5. This causes the injections to be parsed again, resulting in Lua > Vim > Lua > Vim. 6. Now, by the same process, Vim ends up with its range assumed over the whole document. Now the parse is broken and results in broken highlighting and poor performance. It should be fine to instead treat an unparsed node as occupying nothing (i.e. effectively non-existent). Since, either: - The parent was just parsed, hence defining `_regions` - The parent was not just parsed, in which case this node doesn't need to be parsed either. Also, the name `has_regions` is confusing; it seems to simply mean the opposite of "root" or "full_document". However, this PR does not touch it.
* | fix(api): get virtual text with multiple hl properly (#25307)zeertzjq2023-09-22
| |
* | fix(ui): handle virtual text with multiple hl in more cases (#25304)zeertzjq2023-09-22
| |
* | fix(extmarks): inline virt_text support multiple hl groups (#25303)zeertzjq2023-09-22
| |
* | docs: small improvements to compl-autocomplete example (#25299)zeertzjq2023-09-22
| | | | | | | | - Don't complete when there is pending input. - Use vim.list_contains() instead of vim.tbl_contains().
* | vim-patch:9.0.1923: curswant wrong on click with 've' and 'nowrap' set (#25293)zeertzjq2023-09-22
| | | | | | | | | | | | | | | | Problem: curswant wrong on click with 've' and 'nowrap' set Solution: Add w_leftcol to mouse click column. closes: vim/vim#13142 https://github.com/vim/vim/commit/db54e989b5cff3cc6442dfc500e3962cc1c0b6d0
* | build: actually export symbols on macdundargoc2023-09-21
| | | | | | | | | | | | | | | | | | | | | | | | If `-export_dynamic` is not passed to the linker, then Link Time Optimization may inline and remove global functions even though ENABLE_EXPORTS is set to true. Closes https://github.com/neovim/neovim/issues/25295. Closes https://github.com/kevinhwang91/nvim-ufo/issues/162. Closes https://github.com/neovim/neovim/issues/25295. Co-authored-by: Carlo Cabrera <30379873+carlocab@users.noreply.github.com>
* | Merge pull request #25288 from bfredl/tuiassertbfredl2023-09-21
|\ \ | | | | | | fix(tui): don't overwrite an assertion faliure message on exit
| * | fix(tui): don't overwrite an assertion faliure message on exitbfredl2023-09-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If nvim exited with nonzero status this is for one of the two reasons - `:cquit` was invoked. This is used by users and plugins to communicate a result, like a nonzero status will fail a `git commit` operation - There was an internal error or deadly signal. in this case an error message was likely written to stderr or to the screen. In the latter case, the error message was often hidden by the TUI exiting altscreen mode, which erases all visible terminal text. This change prevents this in the latter case, while still cleaning up the terminal properly when `:cquit` was deliberatily invoked. Other cleanup like exiting mouse mode and raw mode is still done.
* | | fix(lsp): handle absence of a trailing newline #25194Sergey Slipchenko2023-09-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes #24339 rust-analyzer sends "Invalid offset" error in such cases. Some other servers handle it specially. LSP spec mentions that "A range is comparable to a selection in an editor". Most editors don't handle trailing newlines the same way Neovim/Vim does, it's clearly visible if it's present or not. With that in mind it's understandable why sending end position as simply the start of the line after the last one is considered invalid in such cases.
* | | fix(lsp): clear codelens on LspDetach (#24903)Jaehwang Jung2023-09-21
|/ / | | | | Also fix incorrect parameters in on_detach callback.
* | Merge pull request #25270 from bfredl/indeterminismbfredl2023-09-21
|\ \ | | | | | | fix(test): fix "indeterminism" warnings in UI tests
| * | fix(test): fix "indeterminism" warnings in UI testsbfredl2023-09-20
| | |
* | | vim-patch:a7aba6ca5033 (#25285)zeertzjq2023-09-21
| | | | | | | | | | | | | | | runtime(doc): format jumplist examples more consistently (vim/vim#13137) https://github.com/vim/vim/commit/a7aba6ca5033a85839d997d29d5ca88a1f2acf8f
* | | build(deps): bump luajit to HEAD - d1a2fef8aChristian Clason2023-09-21
| | |
* | | Merge pull request #25281 from zeertzjq/vim-9.0.1919zeertzjq2023-09-21
|\ \ \ | |_|/ |/| | vim-patch:9.0.1919: Wrong curswant when clicking on empty line or with vsplits
| * | fix(mouse): click on empty line with 'foldcolumn'zeertzjq2023-09-21
| | |
| * | test(ui/float_spec): click in bordered float sets correct curswantzeertzjq2023-09-21
| | |
| * | vim-patch:9.0.1919: Wrong curswant when clicking on empty line or with vsplitszeertzjq2023-09-21
|/ / | | | | | | | | | | | | | | | | | | Problem: Wrong curswant when clicking on empty line or with vsplits. Solution: Don't check for ScreenCols[] before the start of the window and handle empty line properly. closes: vim/vim#13132 https://github.com/vim/vim/commit/03cd697d635f1b0e7ffe21cf8244a8fb755f2ddb
* | vim-patch:9.0.1921: not possible to use the jumplist like a stack (#25278)zeertzjq2023-09-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: not possible to use the jumplist like a stack Solution: Add the 'jumpoptions' setting to make the jumplist a stack. Add an option for using jumplist like tag stack related: vim/vim#7738 closes: vim/vim#13134 ported from NeoVim: - https://neovim.io/doc/user/motion.html#jumplist-stack - neovim/neovim@39094b3 - https://vi.stackexchange.com/questions/18344/how-to-change-jumplist-behavior Based on the feedback in the previous PR, it looks like many people like this option. https://github.com/vim/vim/commit/87018255e3ad0f4dfa03e20318836d24af721caf Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com> Co-authored-by: butwerenotthereyet <58348703+butwerenotthereyet@users.noreply.github.com>
* | fix(statuscolumn): update number hl for each screen line (#25277)zeertzjq2023-09-21
| |
* | vim-patch:9.0.1918Christian Clason2023-09-21
| | | | | | | | | | | | | | | | | | | | | | | | | | patch 9.0.1918: No filetype detection for Authzed filetypes Problem: No filetype detection for Authzed filetypes Solution: Detect the *.zed file extension as authzed filetype closes: vim/vim#13129 https://github.com/vim/vim/commit/5790a54166793554d16f6a85d8824632860b8b37 Co-authored-by: Matt Polzin <mpolzin@workwithopal.com>
* | fix(extmarks): account for rightleft when drawing virt text (#25262)Ibby2023-09-20
| | | | | | Co-authored-by: zeertzjq <zeertzjq@outlook.com>
* | fix(extmarks): fix win_col virt_text drawn on wrong screen line (#25264)zeertzjq2023-09-20
| |
* | feat(lua): add vim.func._memoizeLewis Russell2023-09-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Memoizes a function, using a custom function to hash the arguments. Private for now until: - There are other places in the codebase that could benefit from this (e.g. LSP), but might require other changes to accommodate. - Invalidation of the cache needs to be controllable. Using weak tables is an acceptable invalidation policy, but it shouldn't be the only one. - I don't think the story around `hash_fn` is completely thought out. We may be able to have a good default hash_fn by hashing each argument, so basically a better 'concat'.
* | fix(build): better deps for docLewis Russell2023-09-20
|/
* docs: misc #24561Justin M. Keyes2023-09-20
| | | | fix #24699 fix #25253
* Merge pull request #25261 from bfredl/nolinewrapbfredl2023-09-20
|\ | | | | refactor(grid): unused grid->line_wraps delenda est
| * refactor(grid): unused grid->line_wraps delenda estbfredl2023-09-20
| | | | | | | | | | | | This is not used as part of the logic to actually implement TUI line wrapping In vim (especially gvim) it is used to emulate terminal-style text selection. But in nvim we don't do that, and have no plans to reintroduce it.
* | Merge pull request #25244 from jedrzejboczar/fix-cursor-jump-win-separatorsbfredl2023-09-20
|\ \ | | | | | | fix: avoid ui_grid_cursor_goto when drawing window separators
| * | fix: avoid ui_grid_cursor_goto when drawing window separatorsJędrzej Boczar2023-09-19
| | |
* | | docs: document $XDG environment variables #25227Eduardo Rittner Coelho2023-09-20
| |/ |/|
* | Merge pull request #25096 from glepnir/float_winnewbfredl2023-09-20
|\ \ | | | | | | fix(float): trigger winnew event when float window create
| * | fix(float): trigger winnew event when float window createglepnir2023-09-19
| | |
* | | Merge pull request #25155 from glepnir/fix_winhlbfredl2023-09-20
|\ \ \ | | | | | | | | fix(highlight): winhl receive wrong argument
| * | | fix(highlight): winhl receive wrong argumentglepnir2023-09-19
| | | |
* | | | test(lsp): add normalize_markdown testsMaria José Solano2023-09-20
| | | |
* | | | vim-patch:9.0.1915: r_CTRL-C works differently in visual mode (#25248)zeertzjq2023-09-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: r_CTRL-C works differently in visual mode Solution: Make r_CTRL-C behave consistent in visual mode in terminal and Windows GUI in visual mode, r CTRL-C behaves strange in Unix like environments. It seems to end visual mode, but still is waiting for few more chars, however it never seems to replace it by any characters and eventually just returns back into normal mode. In contrast in Windows GUI mode, r_CTRL-C replaces in the selected area all characters by a literal CTRL-C. Not sure why it behaves like this. It seems in the Windows GUI, got_int is not set and therefore behaves as if any other normal character has been pressed. So remove the special casing of what happens when got_int is set and make it always behave like in Windows GUI mode. Add a test to verify it always behaves like replacing in the selected area each selected character by a literal CTRL-C. closes: vim/vim#13091 closes: vim/vim#13112 https://github.com/vim/vim/commit/476733f3d06876c7ac105e064108c973a57984d3 Co-authored-by: Christian Brabandt <cb@256bit.org>
* | | | fix(lsp)!: deprecate trim_empty_linesMaria José Solano2023-09-19
| | | |
generated by cgit (git 2.34.1) at 2025-06-24 02:16:49 +0000