aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* vim-patch:9.1.0841: tests: still preferring python2 over python3 (#31083)zeertzjq2024-11-04
| | | | | | | | | | | | | | | | | | | Problem: tests: still preferring python2 over python3 Solution: prefer Python 3 when picking a Python program in Vim tests, by checking for the more specific python version first and only when python3 not found, check for the python binary (Yee Cheng Chin) Most OSes have Python 3 mapped to `python3` instead of `python`. Vim tests should prioritize using that instead of Python 2 in case that is still installed on the host system. closes: vim/vim#15986 https://github.com/vim/vim/commit/cef8ab2c75841cee1cd72266aa662fbe54fc0acc Cherry-pick test changes from patch 8.2.{2824,4684}. Co-authored-by: Yee Cheng Chin <ychin.git@gmail.com>
* feat(defaults): unimpaired empty line below/above cursor #30984Yochem van Rosmalen2024-11-04
|
* feat(options)!: disallow setting hidden options #28400Famiu Haque2024-11-04
| | | | | | | | | | | | | | | | | Problem: There are three different ways of marking an option as hidden, `enable_if = false`, `hidden = true` and `immutable = true`. These also have different behaviors. Options hidden with `enable_if = false` can't have their value fetched using Vim script or the API, but options hidden with `hidden = true` or `immutable = true` can. On the other hand, options with `hidden = true` do not error when trying to set their value, but options with `immutable = true` do. Solution: Remove `enable_if = false`, remove the `hidden` property for options, and use `immutable = true` to mark an option as hidden instead. Also make hidden option variable pointers always point to the default value, which allows fetching the value of every hidden option using Vim script and the API. This does also mean that trying to set a hidden option will now give an error instead of just being ignored.
* Merge pull request #30608 from bfredl/cchar2bfredl2024-11-04
|\ | | | | feat(editor): handle new multibyte sequences in normal mode replacement
| * feat(editor): handle new multibyte sequences in normal mode replacementbfredl2024-11-04
| | | | | | | | | | | | | | while the implementation is not tied to screen chars, it is a reasonable expectation to support the same size. If nvim is able to display a multibyte character, it will accept the same character as input, including in normal mode commands like r{char}
* | feat(lsp): multi-client support for signature_helpLewis Russell2024-11-04
|/ | | | | Signatures can be cycled using `<C-s>` when the user enters the floating window.
* ci: work around flaky python tests (#31063)dundargoc2024-11-03
| | | | | It's the same workaround as 88ed9ffcd1c022811ebc8818e153fe94e4741671, which was later removed in f707ce76acb86e064d549dc762f5636af072d3c5 after it turned out to be stable after a while.
* Merge pull request #31059 from zeertzjq/vim-9.1.0832zeertzjq2024-11-03
|\ | | | | vim-patch:9.1.{0832,0835}
| * vim-patch:9.1.0835: :setglobal doesn't work properly for 'ffu' and 'tsrfu'zeertzjq2024-11-03
| | | | | | | | | | | | | | | | | | | | Problem: :setglobal doesn't work properly for 'ffu' and 'tsrfu' when the local value is set (after v9.1.0831) Solution: Check os_flags instead of buffer option variable (zeertzjq). closes: vim/vim#15980 https://github.com/vim/vim/commit/6eda269600b5ca952f28e808c662f67e581933d7
| * vim-patch:9.1.0832: :set doesn't work for 'cot' and 'bkc' after :setlocalzeertzjq2024-11-03
|/ | | | | | | | | Problem: :set doesn't work for 'cot' and 'bkc' after :setlocal. Solution: clear the local flags when using :set (zeertzjq). closes: vim/vim#15981 https://github.com/vim/vim/commit/46dcd84d242db6b053cb5b777c896cede9ad9b27
* fix(treesitter): close InspectTree/EditQuery window on BufUnload (#31036)zeertzjq2024-11-03
| | | | | | Problem: The window opened :InspectTree or :EditQuery isn't closed when the source buffer is unloaded, even though it is closed when the buffer is hidden. Solution: Also close the window on BufUnload.
* vim-patch:9.1.0831: 'findexpr' can't be used as lambad or Funcref (#31058)zeertzjq2024-11-03
| | | | | | | | | | | | | Problem: 'findexpr' can't be used for lambads (Justin Keyes) Solution: Replace the findexpr option with the findfunc option (Yegappan Lakshmanan) related: vim/vim#15905 closes: vim/vim#15976 https://github.com/vim/vim/commit/a13f3a4f5de9c150f70298850e34747838904995 Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
* vim-patch:9.1.0830: using wrong highlight group for spaces for popupmenu ↵zeertzjq2024-11-03
| | | | | | | | | | | | | (#31054) Problem: using wrong highlight group for spaces for popupmenu Solution: use original attribute instead of combined attributed (glepnir) closes: vim/vim#15978 https://github.com/vim/vim/commit/bc10be7a4060748ed1876ab91cf53a2a8701ac13 Co-authored-by: glepnir <glephunter@gmail.com>
* vim-patch:a95d6a3: runtime(doc): remove stray sentence in pi_netrw.txt (#31053)zeertzjq2024-11-03
| | | | | | | closes: vim/vim#15971 https://github.com/vim/vim/commit/a95d6a3d641dd065cccb1e76863dd3450ee5ce04 Co-authored-by: S. B. Tam <cpplearner@outlook.com>
* fix(health): better layout of vim.treesitter health checkChristian Clason2024-11-02
| | | | | | | | Problem: Long lists of available parsers make it hard to see WASM status. Solution: Add separate headings for "treesitter features" (ABI, WASM) and "treesitter parsers". Also add minimum supported ABI version.
* vim-patch:9.1.0826: filetype: sway files are not recognizedChristian Clason2024-11-02
| | | | | | | | | | | | | | | | | | Problem: filetype: sway files are not recognized Solution: detect '*.sw' files as sway filetype, include a filetype plugin (Riley Bruins) References: https://github.com/FuelLabs/sway. Comments taken from their syntax documentation. File extension taken from the same documentation/GitHub's own recognition of these file types closes: vim/vim#15973 https://github.com/vim/vim/commit/84b5b1c660beb2f9e27de70687e41d39a023ae81 Co-authored-by: Riley Bruins <ribru17@hotmail.com>
* vim-patch:d181baf: runtime(typst): synchronize updates from the upstream ↵Christian Clason2024-11-02
| | | | | | | | | | | | | typst.vim 2 commits included from the upstream: - https://github.com/kaarmu/typst.vim/commit/2a4a0e0662f2f882403af7200b4249c564a621ab - https://github.com/kaarmu/typst.vim/commit/50e89f481102d5c9ef6990b9f8086c0c7d64bff6 https://github.com/vim/vim/commit/d181bafd0bb53f3caaf15a95a329a31d8208206b Co-authored-by: Yinzuo Jiang <jiangyinzuo@foxmail.com>
* refactor(options): remove `get_option_value_strict`Famiu Haque2024-11-02
| | | | | | Problem: `get_option_value_for` can perfectly replace `get_option_value_strict`, making the latter redundant. Solution: Remove `get_option_value_strict`
* fix(lua): show stacktrace for error in vim.on_key() callback (#31021)zeertzjq2024-11-02
|
* vim-patch:26113e5: runtime(doc): Include netrw-gp in TOC (#31032)zeertzjq2024-11-02
| | | | | | | closes: vim/vim#7627 https://github.com/vim/vim/commit/26113e5ae3c4762ab718d5f006afa71f67e6f459 Co-authored-by: Ernesto Elsäßer <ernesto.elsaesser@me.com>
* refactor(options): unify `put_set(num|bool|string)` (#30993)Famiu Haque2024-11-02
| | | | | | | | | | | | | Problem: There are three separate functions for printing the `:set` command for an setting an option to a file descriptor. These functions are used when creating the session file for an option. Having a function for each type increase code duplication and also makes it harder to add logic for new option types. Solution: Replace `put_set(num|bool|string)` with a single `put_set` function which works for all option types, this reduces code duplication and also makes it trivial to add support for more option types in the future.
* vim-patch:b5e7da1: runtime(doc): mention 'iskeyword' at :h charclass() (#31026)zeertzjq2024-11-01
| | | | | | | fixes: vim/vim#15965 https://github.com/vim/vim/commit/b5e7da1f27241f7d770d342009e2fb443e45e6ce Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:9.1.0824: too many strlen() calls in register.c (#31022)zeertzjq2024-11-01
| | | | | | | | | | | Problem: too many strlen() calls in register.c Solution: refactor code, add string_T struct to keep track of string lengths (John Marriott) closes: vim/vim#15952 https://github.com/vim/vim/commit/79f6ffd388299ef3b1c95cbe658785e6e66df144 Co-authored-by: John Marriott <basilisk@internode.on.net>
* feat(lsp)!: remove client-server handlers from vim.lsp.handlersLewis Russell2024-11-01
| | | | | | | | | | - Partition the handlers in vim.lsp.handlers as: - client to server response handlers (RCS) - server to client request handlers (RSC) - server to client notification handlers (NSC) Note use string indexes instead of protocol.methods for improved typing in LuaLS (tip: use hover on RCS, RSC or NSC).
* fix(lsp): hover border type can be string (#31013)nikolightsaber2024-11-01
| | | | | Border type can also be a string as defined in `api-win_config` Co-authored-by: Nikolai Devolder <nikolai.devolder@yamabiko.eu>
* feat(lua): allow vim.on_key() callback to consume the key (#30939)errael2024-11-01
|
* Merge pull request #31011 from lewis6991/refactor/loaderLewis Russell2024-10-31
|\
| * refactor(loader): format annotationsLewis Russell2024-10-31
| |
| * refactor(loader): use the term stat instead of hashLewis Russell2024-10-31
| |
| * refactor(loader): remove Loader table and use localsLewis Russell2024-10-31
| |
| * refactor(loader): rename typesLewis Russell2024-10-31
| |
| * refactor(loader): inline Loader.load into Loader.loadfileLewis Russell2024-10-31
| |
| * refactor(loader): simplify Loader.loader_libLewis Russell2024-10-31
| |
| * refactor(loader): simplify Loader.write/readLewis Russell2024-10-31
| |
| * perf(loader): reduce calls to Loader.cache_fileLewis Russell2024-10-31
| |
| * refactor(loader): remove unused _topmodsLewis Russell2024-10-31
|/
* fix: another round of type annotation fixesLewis Russell2024-10-31
|
* Merge pull request #31008 from zeertzjq/vim-3d7e567zeertzjq2024-10-31
|\ | | | | vim-patch: netrw fixes
| * vim-patch:4d61800: runtime(netrw): fix E874 when browsing remote directory ↵zeertzjq2024-10-31
| | | | | | | | | | | | | | | | | | | | which contains `~` character closes: vim/vim#15964 https://github.com/vim/vim/commit/4d618006ecfd2557806d8af488f70b3e46878d70 Co-authored-by: Tom Benham <tom.benham13@gmail.com>
| * vim-patch:8b0fa7a: runtime(netrw): make :Launch/Open autoloadablezeertzjq2024-10-31
| | | | | | | | | | | | | | | | | | | | fixes: vim/vim#15959 closes: vim/vim#15962 https://github.com/vim/vim/commit/8b0fa7a565d8aec306e5755307d182fa7d81e65f Co-authored-by: Christian Brabandt <cb@256bit.org> Co-authored-by: Aliaksei Budavei <0x000c70@gmail.com>
| * vim-patch:9f32069: runtime(netrw): fix regression with x mapping on Cygwinzeertzjq2024-10-31
| | | | | | | | | | | | | | | | | | related: vim/vim#13687 https://github.com/vim/vim/commit/9f32069b8c4f74aa6af47e2f0ec07f2745feac57 Co-authored-by: Christian Brabandt <cb@256bit.org> Co-authored-by: K.Takata <kentkt@csc.jp>
| * vim-patch:aa2ce6f: runtime(netrw): fix filetype detection for remote fileszeertzjq2024-10-31
| | | | | | | | | | | | | | | | | | | | | | fixes: vim/vim#15961 while at it, remove the Decho comments in the s:NetrwOptionsRestore() function https://github.com/vim/vim/commit/aa2ce6f58005bc3b81be2bf42f84ffd01ce22d57 Co-authored-by: Christian Brabandt <cb@256bit.org>
| * vim-patch:d69ffbe: runtime(netrw): add missing change for s:redir()zeertzjq2024-10-31
| | | | | | | | | | | | | | | | Somehow, that change got lost in commit 70197885 https://github.com/vim/vim/commit/d69ffbe4bc2196c4fc2b9377167a9a194213a686 Co-authored-by: Christian Brabandt <cb@256bit.org>
| * vim-patch:7019788: runtime(netrw): improve netrw's open-handling furtherzeertzjq2024-10-31
| | | | | | | | | | | | | | | | closes: vim/vim#15956 https://github.com/vim/vim/commit/70197885a8957071e4ab6816141ce6e8026635c6 Co-authored-by: Enno <Konfekt@users.noreply.github.com>
| * vim-patch:7c96776: runtime(netrw): fix syntax error in netrwPlugin.vimzeertzjq2024-10-31
| | | | | | | | | | | | https://github.com/vim/vim/commit/7c96776729a671b7c5f6be81bc29d860920ea1c1 Co-authored-by: Christian Brabandt <cb@256bit.org>
| * vim-patch:3d7e567: runtime(netrw): simplify gx file handlingzeertzjq2024-10-31
|/ | | | | | | | | | | | | | | | | | | | | | It did not work very well, at least on Debian 12, and I am not sure Git Bash and WSL, for example, were taken care of as maintenance stalled. The whole logic was somewhat convoluted with some parts repeatedly invoking failed commands. The file handling was outdated, for example, nowadays Netscape is rarely used, and also opinionated, for example mainly Microsoft Paint and Gimp for Image files. Instead, let's use (xdg-)open and similar commands on other systems which respects the user's preferences. closes: vim/vim#15721 https://github.com/vim/vim/commit/3d7e567ea7392e43a90a6ffb3cd49b71a7b59d1a Co-authored-by: Konfekt <Konfekt@users.noreply.github.com> Co-authored-by: Luca Saccarola <96259932+saccarosium@users.noreply.github.com>
* vim-patch:6be21b9: runtime(debversions): Add plucky (25.04) as Ubuntu ↵Christian Clason2024-10-31
| | | | | | | | | | release name closes: vim/vim#15882 https://github.com/vim/vim/commit/6be21b937db1c088c4d191e4569989eb078adb45 Co-authored-by: Simon Quigley <tsimonq2@ubuntu.com>
* vim-patch:9.1.0823: filetype: Zephyr overlay files not recognizedChristian Clason2024-10-31
| | | | | | | | | | | | | | | | Problem: filetype: Zephyr overlay files not recognized Solution: detect '*.overlay' files as dts filetype, include syntax tests for DTS files (Xudong Zheng) Reference: https://docs.zephyrproject.org/latest/build/dts/howtos.html closes: vim/vim#15963 https://github.com/vim/vim/commit/a68bd6f089239a51ba90026b18109707e601b107 Co-authored-by: Xudong Zheng <7pkvm5aw@slicealias.com>
* feat(highlight): make `PmenuMatch` and `PmenuMatchSel` boldEvgeni Chasnovski2024-10-31
| | | | | | | | | | | | | | Problem: both `PmenuMatch` and `PmenuMatchSel` can provide helpful information about characters which actually match query in completion candidates. This is not as useful with default regular match, but much more useful with 'completopt+=fuzzy'. Solution: make both highlight groups bold. This will also affect (i.e. benefit) other color schemes which do not define groups separately. This is possible since the recently merged changes to `PmenuMatch` and `PmenuMatchSel` combine attributes with underlying "base" groups. See PR 29980.
* test: fix files being left behind (#31004)zeertzjq2024-10-31
|
generated by cgit (git 2.34.1) at 2025-06-24 14:17:18 +0000