aboutsummaryrefslogtreecommitdiff
path: root/runtime/lua/vim
Commit message (Collapse)AuthorAge
...
* vim-patch:9.1.1321: filetype: MS ixx and mpp files are not recognizedChristian Clason2025-04-19
| | | | | | | | | | | | Problem: filetype: MS ixx and mpp files are not recognized Solution: detect *.mpp and *.ixx files as c++ filetype (Hampus Avekvist) closes: vim/vim#17155 https://github.com/vim/vim/commit/aee34ef23e08a944f87d6bb4f972c56ba88dc6dd Co-authored-by: Hampus Avekvist <hampus.avekvist@hey.com>
* vim-patch:cb3b752: runtime(doc): clarify "nearest" value for 'completeopt' ↵zeertzjq2025-04-19
| | | | | | | | | (#33534) closes: vim/vim#17146 https://github.com/vim/vim/commit/cb3b752f9523060d3feaee33049d2092c288fca2 Co-authored-by: Girish Palya <girishji@gmail.com>
* Merge pull request #33519 from zeertzjq/vim-9.1.1314zeertzjq2025-04-19
|\ | | | | vim-patch:9.1.{1314,1318}: max allowed string width too small
| * vim-patch:9.1.1318: tests: test_format failszeertzjq2025-04-18
| | | | | | | | | | | | | | | | | | | | Problem: tests: test_format fails (after 9.1.1314). Solution: Increase the string size. Add missing test_format.res in NEW_TESTS_RES (zeertzjq). closes: vim/vim#17144 https://github.com/vim/vim/commit/e9a27ef37395a0130f99e21b288b7765f0e38236
* | fix(spell): save spell files to stdpath('data')/site/spell #33528Au.2025-04-18
|/
* fix(lsp): opts.reuse_win does not jump if buf is already open #33476Au.2025-04-17
| | | | | | | | | | | | | | | | Problem: `vim.lsp.buf.[implementation|definition|...]({ reuse_win = true })` does not jump cursor to existing window if buffer is already open. Steps to reproduce: 1. `nvim repro.lua` 2. Insert anything that lsp can read to open the library definition/implementation, e.g., `vim.keymap.set` 3. open `repro.lua` buffer and the library buffer side by side. 4. type `gd` over `set` to jump to the library definition. The open buffer is scrolled to the target line, but cursor does not jump. Solution: Call nvim_set_current_win if necessary.
* refactor(lsp): gen_lspLewis Russell2025-04-17
| | | | | | | | | | - Simplify usage: - Instead of `nvim -l src/gen/gen_lsp.lua gen` now just run `./src/gen/gen_lsp.lua` - Removed `--methods` and `--capabilities` options. - Improved rendering code in various areas.
* feat(lsp): use stricter types for methodsLewis Russell2025-04-17
| | | | | | | | | | | | This change modifies gen_lsp.lua so alias types are generated for various types of lsp methods to distinguish between notifications and requests: - vim.lsp.protocol.Method.ServerToClient.Request - vim.lsp.protocol.Method.ServerToClient.Notification - vim.lsp.protocol.Method.ClientToServer.Request - vim.lsp.protocol.Method.ClientToServer.Notification These types are then used instead of `string` where appropriate.
* vim-patch:9.1.1307: make syntax does not reliably detect different flavors ↵zeertzjq2025-04-17
| | | | | | | | | | | | | | | (#33498) Problem: GNU extensions, such as `ifeq` and `wildcard` function, are highlighted in BSDmakefile Solution: detect BSD, GNU, or Microsoft implementation according to filename, user-defined global variables, or file contents closes: vim/vim#17089 https://github.com/vim/vim/commit/f35bd76b31e6cd62bcc47e401887059b8503c5cc Co-authored-by: Eisuke Kawashima <e-kwsm@users.noreply.github.com> Co-authored-by: Roland Hieber <rohieb@users.noreply.github.com>
* Merge pull request #33383 from zeertzjq/vim-9.1.1284zeertzjq2025-04-17
|\ | | | | vim-patch:9.1.{1262,1284,1296,1306,1309}
| * vim-patch:9.1.1296: completion: incorrect truncation logiczeertzjq2025-04-17
| | | | | | | | | | | | | | | | | | | | | | | | Problem: completion: incorrect truncation logic (after: v9.1.1284) Solution: replace string allocation with direct screen rendering and fixe RTL/LTR truncation calculations (glepnir) closes: vim/vim#17081 https://github.com/vim/vim/commit/d4dbf822dcb9fd95379bebab85def391e1179b21 Co-authored-by: glepnir <glephunter@gmail.com>
| * vim-patch:9.1.1284: not possible to configure pum truncation charzeertzjq2025-04-17
| | | | | | | | | | | | | | | | | | | | | | | | | | Problem: not possible to configure the completion menu truncation character Solution: add the "trunc" suboption to the 'fillchars' setting to configure the truncation indicator (glepnir). closes: vim/vim#17006 https://github.com/vim/vim/commit/b87620466c6500fb37fd9be1016a27fa9626749a Co-authored-by: glepnir <glephunter@gmail.com>
* | fix(treesitter): fix `:InspectTree` incorrect injectionsyuukibarns2025-04-16
|/
* fix(vim.system): unclear non-executable message #33455Justin M. Keyes2025-04-16
| | | | | | | | | | | | | | | | | | Problem: When a command is not found or not executable, the error message gives no indication about what command was actually tried. Solution: Always append the command name to the error message. BEFORE: E5108: Error executing lua …/_system.lua:248: ENOENT: no such file or directory AFTER: E5108: Error executing lua …/_system.lua:249: ENOENT: no such file or directory: "foo" fix #33445
* vim-patch:9.1.1308: completion: cannot order matches by distance to cursor ↵zeertzjq2025-04-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (#33491) Problem: During insert-mode completion, the most relevant match is often the one closest to the cursor—frequently just above the current line. However, both `<C-N>` and `<C-P>` tend to rank candidates from the current buffer that appear above the cursor near the bottom of the completion menu, rather than near the top. This ordering can feel unintuitive, especially when `noselect` is active, as it doesn't prioritize the most contextually relevant suggestions. Solution: This change introduces a new sub-option value "nearest" for the 'completeopt' setting. When enabled, matches from the current buffer are prioritized based on their proximity to the cursor position, improving the relevance of suggestions during completion (Girish Palya). Key Details: - Option: "nearest" added to 'completeopt' - Applies to: Matches from the current buffer only - Effect: Sorts completion candidates by their distance from the cursor - Interaction with other options: - Has no effect if the `fuzzy` option is also present This feature is helpful especially when working within large buffers where multiple similar matches may exist at different locations. You can test this feature with auto-completion using the snippet below. Try it in a large file like `vim/src/insexpand.c`, where you'll encounter many potential matches. You'll notice that the popup menu now typically surfaces the most relevant matches—those closest to the cursor—at the top. Sorting by spatial proximity (i.e., contextual relevance) often produces more useful matches than sorting purely by lexical distance ("fuzzy"). Another way to sort matches is by recency, using an LRU (Least Recently Used) cache—essentially ranking candidates based on how recently they were used. However, this is often overkill in practice, as spatial proximity (as provided by the "nearest" option) is usually sufficient to surface the most relevant matches. ```vim set cot=menuone,popup,noselect,nearest inf def SkipTextChangedIEvent(): string # Suppress next event caused by <c-e> (or <c-n> when no matches found) set eventignore+=TextChangedI timer_start(1, (_) => { set eventignore-=TextChangedI }) return '' enddef autocmd TextChangedI * InsComplete() def InsComplete() if getcharstr(1) == '' && getline('.')->strpart(0, col('.') - 1) =~ '\k$' SkipTextChangedIEvent() feedkeys("\<c-n>", "n") endif enddef inoremap <silent> <c-e> <c-r>=<SID>SkipTextChangedIEvent()<cr><c-e> inoremap <silent><expr> <tab> pumvisible() ? "\<c-n>" : "\<tab>" inoremap <silent><expr> <s-tab> pumvisible() ? "\<c-p>" : "\<s-tab>" ``` closes: vim/vim#17076 https://github.com/vim/vim/commit/b156588eb707a084bbff8685953a8892e1e45bca Co-authored-by: Girish Palya <girishji@gmail.com>
* vim-patch:9.1.1299: filetype: mbsyncrc files are not recognizedChristian Clason2025-04-14
| | | | | | | | | | | | | | | | | | | | | | | | Problem: filetype: mbsyncrc files are not recognized Solution: detect isyncrc and "*.mbsyncrc" files as mbsync filetype, include filetype and syntax plugin (Pierrick Guillaume) mbsync is a command line application which synchronizes mailboxes; currently Maildir and IMAP4 mailboxes are supported. New messages, message deletions and flag changes can be propagated both ways; the operation set can be selected in a fine-grained manner. References: mbsync syntax overview: mbsync manual (isync v1.4.4) https://isync.sourceforge.io/mbsync.html Upstream support for the mbsync filetype. Original plugin: https://github.com/Fymyte/mbsync.vim closes: vim/vim#17103 https://github.com/vim/vim/commit/836b87d6998a1f18783afdc41c90ae1f38c9c3e9 Co-authored-by: Pierrick Guillaume <pguillaume@fymyte.com>
* vim-patch:f4b1a60: runtime(doc): update options.txt and clarify 'wildmode' ↵zeertzjq2025-04-14
| | | | | | | | | | | further related: vim/vim#17100 https://github.com/vim/vim/commit/f4b1a60dd145c8dddd2b6a37699e96772cd69402 Co-authored-by: Christian Brabandt <cb@256bit.org> Co-authored-by: Girish Palya <girishji@gmail.com>
* vim-patch:eded336: runtime(doc): Improve 'wildmode' setting desciptionzeertzjq2025-04-14
| | | | | | | | closes: vim/vim#17100 https://github.com/vim/vim/commit/eded33621be29b9fdc51466efdc946fa8d3e756f Co-authored-by: Girish Palya <girishji@gmail.com>
* fix(treesitter): injected lang ranges may cross capture boundaries #32549Riley Bruins2025-04-13
| | | | | | | | | | | | | Problem: treesitter injected language ranges sometimes cross over the capture boundaries when `@combined`. Solution: Clip child regions to not spill out of parent regions within languagetree.lua, and only apply highlights within those regions in highlighter.lua. Co-authored-by: Cormac Relf <web@cormacrelf.net>
* docs: misc #33330Justin M. Keyes2025-04-12
|
* feat(defaults): shelltemp=false #33012Alexej Kowalew2025-04-12
| | | | Co-authored-by: zeertzjq <zeertzjq@outlook.com> Co-authored-by: Justin M. Keyes <justinkz@gmail.com>
* fix(vim.version): vim.VersionRange:has(<prerelease>) (#33324)Phạm Bình An2025-04-11
| | | | | | | | | | | | Problem: `vim.version.range('>=0.10'):has('0.12.0-dev')` returns false, which is wrong per semver. Solution: `vim.VersionRange:has()` shouldn't have special handling for prereleases (Why would we need it when `__eq`, `__lt`, `__le` already handle prereleases?). Closes #33316
* vim-patch:5c84d12: runtime(filetype): make shell filetype detection more ↵zeertzjq2025-04-11
| | | | | | | | | robust (#33421) closes: vim/vim#17063 https://github.com/vim/vim/commit/5c84d12df104e976e8f56c43f9f975e54d9fd779 Co-authored-by: Aliaksei Budavei <0x000c70@gmail.com>
* vim-patch:9.1.1212: filetype: logrotate'd pacmanlogs are not recognized (#33412)zeertzjq2025-04-10
| | | | | | | | | | | Problem: filetype: logrotate'd pacmanlogs are not recognized Solution: also detect pacman.log* files as pacmanlog filetype, remove BufNewFile autocmd (Eisuke Kawashima) closes: vim/vim#16873 https://github.com/vim/vim/commit/20d23ce93b84ea199d5ea56d7ec86f5e6846d6cc Co-authored-by: Eisuke Kawashima <e-kwsm@users.noreply.github.com>
* fix(lsp): "bold" border for vim.lsp.buf.hover #33395Siddhant Agarwal2025-04-09
| | | | | | Problem: vim.lsp.buf.hover allows a bold border size which hasn't been defined Solution: Define the bold border size for vim.lsp.buf.hover
* feat(health): summary in section heading #33388Yochem van Rosmalen2025-04-09
| | | | | | | | Problem: As checkhealth grows, it is increasingly hard to quickly glance through the information. Solution: Show a summary of ok, warn, and error outputs per section.
* vim-patch:9.1.1288: Using wrong window in ll_resize_stack() (#33397)zeertzjq2025-04-09
| | | | | | | | | | Problem: Using wrong window in ll_resize_stack() (after v9.1.1287) Solution: Use "wp" instead of "curwin", even though they are always the same value. Fix typos in documentation (zeertzjq). closes: vim/vim#17080 https://github.com/vim/vim/commit/b71f1309a210bf8f61a24f4eda336de64c6f0a07
* vim-patch:9.1.1283: quickfix stack is limited to 10 itemszeertzjq2025-04-08
| | | | | | | | | | | | | | Problem: quickfix and location-list stack is limited to 10 items Solution: add the 'chistory' and 'lhistory' options to configure a larger quickfix/location list stack (64-bitman) closes: vim/vim#16920 https://github.com/vim/vim/commit/88d41ab270a8390a43da97a903b1a4d76b89d330 Co-authored-by: 64-bitman <60551350+64-bitman@users.noreply.github.com> Co-authored-by: Hirohito Higashi <h.east.727@gmail.com>
* vim-patch:9.1.1286: filetype: help files not detected when 'iskeyword' ↵zeertzjq2025-04-08
| | | | | | | | | | | includes ":" (#33377) Problem: Help files not detected when 'iskeyword' includes ":". Solution: Do not use \< and \> in the pattern (zeertzjq). fixes: vim/vim#17069 closes: vim/vim#17071 https://github.com/vim/vim/commit/e370141bf41919642061ee2e78340dca84678712
* fix(treesitter): not refreshing virtualtext contents #33361Dmitry Zolotukhin2025-04-07
| | | | | | | | Problem: In some cases, when treesitter is enabled, deleting a line below virtualtext will not refresh all updated lines. https://github.com/neovim/neovim/issues/33358 Solution: Revert a part of https://github.com/neovim/neovim/pull/31324 to ensure that the full range (with virtual lines) is refreshed.
* fix(health): expecting nonexistent "inotifywait" function #33312Felipe Lema2025-04-07
| | | | | | | Problem: 55e4301036bb938474fc9768c41e28df867d9286 changed the program name but not the function name. Solution: Fix the healthcheck.
* refactor(lsp): deprecate client_is_stopped #33342Justin M. Keyes2025-04-06
| | | | | | | | Problem: `client_is_stopped(…)` is an alias for `not get_client_by_id(…)`. And it's not used anywhere in our codebase. Solution: Deprecate it.
* fix(vim.hl): nvim_buf_del_extmark on invalid buffer #33331phanium2025-04-05
| | | | | | | Problem: nvim_buf_del_extmark error if buffer is destroyed before timer stops Solution: check nvim_buf_is_valid.
* docs: clipboard, eval #33223Justin M. Keyes2025-04-05
|
* vim-patch:9.1.1276: inline word diff treats multibyte chars as word char ↵zeertzjq2025-04-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (#33323) Problem: inline word diff treats multibyte chars as word char (after 9.1.1243) Solution: treat all non-alphanumeric characters as non-word characters (Yee Cheng Chin) Previously inline word diff simply used Vim's definition of keyword to determine what is a word, which leads to multi-byte character classes such as emojis and CJK (Chinese/Japanese/Korean) characters all classifying as word characters, leading to entire sentences being grouped as a single word which does not provide meaningful information in a diff highlight. Fix this by treating all non-alphanumeric characters (with class number above 2) as non-word characters, as there is usually no benefit in using word diff on them. These include CJK characters, emojis, and also subscript/superscript numbers. Meanwhile, multi-byte characters like Cyrillic and Greek letters will still continue to considered as words. Note that this is slightly inconsistent with how words are defined elsewhere, as Vim usually considers any character with class >=2 to be a "word". related: vim/vim#16881 (diff inline highlight) closes: vim/vim#17050 https://github.com/vim/vim/commit/9aa120f7ada592ed03b37f4de8ee413c5385f123 Co-authored-by: Yee Cheng Chin <ychin.git@gmail.com>
* feat(lsp.util): deprecate vim.lsp.util.stylize_markdownLewis Russell2025-04-04
| | | | It's not used anywhere.
* fix: bug in stylize_markdownLewis Russell2025-04-04
| | | | `stripped` and `markdown_lines` are iterated together so must have the same length.
* feat(defaults): store spellfile in stdpath('data') #33048Yochem van Rosmalen2025-04-04
| | | | | | | | | | | Problem: First rtp directory is unpredictable and not in line with XDG base spec. Solution: Use stdpath('data')/spell as directory if 'spellfile' is not set. Co-authored-by: zeertzjq <zeertzjq@outlook.com> Co-authored-by: Justin M. Keyes <justinkz@gmail.com>
* vim-patch:9.1.1271: filetype: Power Query files are not recognizedChristian Clason2025-04-04
| | | | | | | | | | | | | | | | | | | | | | | | | | Problem: filetype: Power Query files are not recognized Solution: detect '*.pq' as pq filetype, include pq syntax and filetype plugin (Anarion Dunedain) Microsoft Power Query provides a powerful data import experience that encompasses many features. Power Query works with desktop Analysis Services, Excel, and Power BI workbooks, in addition to many online services, such as Fabric, Power BI service, Power Apps, Microsoft 365 Customer Insights, and more. A core capability of Power Query is to filter and combine, that is, to mash-up data from one or more of a rich collection of supported data sources. Any such data mashup is expressed using the Power Query M formula language. The M language is a functional, case sensitive language similar to F#. Reference: - Power Query M formula language overview: https://learn.microsoft.com/en-us/powerquery-m/ closes: vim/vim#17045 https://github.com/vim/vim/commit/e74ec3f523a152f62a37cc3ab476f0e5a2e812c6 Co-authored-by: Anarion Dunedain <anarion80@gmail.com>
* docs(diagnostic): mention `severity` in `Opts.VirtualLines` (#33293)Evgeni Chasnovski2025-04-03
| | | | | | | Problem: `severity` field is recognized by `vim.diagnostic.Opts.VirtualLines`, but it is not explicitly documented. Solution: document it.
* feat(vim.hl): allow multiple timed highlights simultaneously #33283Siddhant Agarwal2025-04-03
| | | | | | | | | Problem: Currently vim.hl.range only allows one timed highlight. Creating another one, removes the old one. Solution: vim.hl.range now returns a timer and a function. The timer keeps track of how much time is left in the highlight and the function allows you to clear it, letting the user decide what to do with old highlights.
* vim-patch:9.1.1268: filetype: dax files are not recognizedChristian Clason2025-04-03
| | | | | | | | | | | | | | | | | | | | | Problem: filetype: dax files are not recognized Solution: detect "*.dax" as dax filetype, include dax filetype and syntax plugin (Anarion Dunedain) Data Analysis Expressions (DAX) is a formula expression language used in Analysis Services, Power BI, and Power Pivot in Excel. DAX formulas include functions, operators, and values to perform advanced calculations and queries on data in related tables and columns in tabular data models. DAX language overview: - https://learn.microsoft.com/en-us/dax/dax-overview closes: vim/vim#17035 https://github.com/vim/vim/commit/7f518e044fbc60cffdf2c0f611cc8c4dc35c338c Co-authored-by: Anarion Dunedain <anarion80@gmail.com>
* Merge pull request #32686 from lewis6991/lsp-rpc-perfLewis Russell2025-04-01
|\ | | | | perf(lsp): improve rpc loop performance (with shim)
| * refactor: add basic stringbuffer shimLewis Russell2025-03-31
| |
| * perf(lsp): use string.buffer for rpc loopMathias Fussenegger2025-03-31
| | | | | | | | | | | | | | | | | | | | Avoids some table allocations. In a quick test over 50000 iterations it reduces the time from 130ms to 74 ms For the test setup details see: https://github.com/mfussenegger/nvim-dap/pull/1394#issue-2725352391
| * perf(lsp): optimize content length extraction from rpc headersMathias Fussenegger2025-03-31
| | | | | | | | | | | | - No redundant `:gsub` to turn `-` in `Content-Length` into `_` - No table allocations only to add and later get the content-length header
* | docs(eval): fix dict param type of mapsetSean Dewar2025-04-01
| | | | | | | | Match maparg's return type.
* | docs(eval): fix lnum type for functions using tv_get_lnumSean Dewar2025-04-01
|/ | | | | | | These occurrences also accept string, which is used like in getline. Also make the lnum field of vim.fn.sign_placelist.list.item optional, as it can be omitted like vim.fn.sign_place.dict's.
* fix(lsp): better handling of "*" configsLewis Russell2025-03-31
| | | | | | | | | | | | | | | Problem: If a config name contains "*" it causes rtp discovery of `lsp/` to consider the `*` as a wildcard and could lead to strange and unintended behaviour. For example, accessing the `'*'` config from a `lsp/` file would cause an infinite loop. Solution: - Explicitly disallow a config name from containing wildcards, with the exception of `'*'`. - When Resolving `'*'` config, skip the rtp step.
* feat(float): 'winborder' "bold" style #33189glepnir2025-03-31
|
generated by cgit (git 2.34.1) at 2026-10-25 19:23:03 +0000