aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* ci: bump actions/create-github-app-token from 1 to 2dependabot[bot]2025-04-06
| | | | | | | | | | | | | | | Bumps [actions/create-github-app-token](https://github.com/actions/create-github-app-token) from 1 to 2. - [Release notes](https://github.com/actions/create-github-app-token/releases) - [Commits](https://github.com/actions/create-github-app-token/compare/v1...v2) --- updated-dependencies: - dependency-name: actions/create-github-app-token dependency-version: '2' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
* 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.
* build: bump NVIM_API_LEVEL #33340Justin M. Keyes2025-04-05
| | | | | Bumping NVIM_API_LEVEL is pretty much required after every major release, because it's also used to correlated Lua stdlib changes to a Nvim version.
* 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>
* vim-patch:b8d5c85: runtime(doc): update WinScrolled documentation (#33322)zeertzjq2025-04-05
| | | | | | | closes: vim/vim#17036 https://github.com/vim/vim/commit/b8d5c8509998f3a97ffe42f674352b07749cd119 Co-authored-by: Christian Brabandt <cb@256bit.org>
* 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.
* fix(messages): verbose message emitted without kind #33305luukvbaal2025-04-04
| | | | | Problem: Successive autocmd verbose messages may be emitted without a kind. Solution: Always set the kind when preparing to emit a verbose message.
* 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>
* vim-patch:6099db9: runtime(sh): Update syntax file, command substitution ↵Christian Clason2025-04-04
| | | | | | | | | | | | | | | | opening paren at EOL Allow the opening parenthesis of a command substitution to appear at EOL. This fixes the issue raised in https://github.com/vim/vim/issues/17026#issuecomment-2774112284. closes: vim/vim#17044 https://github.com/vim/vim/commit/6099db9a60d1c047bf9c8feee3e1689c4e653250 Co-authored-by: Doug Kearns <dougkearns@gmail.com>
* Merge pull request #33282 from glepnir/vim-9.1.1269zeertzjq2025-04-04
|\ | | | | vim-patch:9.1.{1269,1272}
| * vim-patch:9.1.1272: completion: in keyword completion Ctrl_P cannot go back ↵glepnir2025-04-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | after Ctrl_N Problem: completion: in keyword completion Ctrl_P cannot go back after Ctrl_N Solution: in find_compl_when_fuzzy() always return first match of array, after Ctrl_P use compl_shown_match->cp_next instead of compl_first_match. (glepnir) closes: vim/vim#17043 https://github.com/vim/vim/commit/3e50a28a03d136c1e0c1f4fabe50d97faaf08c5c Co-authored-by: glepnir <glephunter@gmail.com>
| * vim-patch:9.1.1269: completion: compl_shown_match is updated when starting ↵glepnir2025-04-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | keyword completion Problem: compl_shown_match is updated when starting keyword completion and does not include fuzzy matching. Solution: Do not update compl_shown_match when starting keyword completion, since it is the one already selected by the keyword completion direction. (glepnir) closes: vim/vim#17033 https://github.com/vim/vim/commit/e4e4d1c381e9d0af55f6111e9bcaf98ad60461fc Co-authored-by: glepnir <glephunter@gmail.com>
* | test(plugin/shada_spec): failure if timezone isn't a whole hour ahead of UTC ↵tstsrt2025-04-04
| | | | | | | | | | | | | | | | | | (#33257) Problem: When running functional tests locally, test `syntax/shada.vim works` fails if the local timezone is not a whole number of hours ahead of UTC. Solution: Use '!%M' for minute format so that UTC is used in the expected timestamp instead of the local timezone, just like '%H' for hours.
* | test(lua/hl_spec): fix hang on exit with ASAN (#33298)zeertzjq2025-04-04
| |
* | 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.
* | test(lua/secure_spec): fix failure with long path (#33280)zeertzjq2025-04-03
| | | | | | Ref #33278
* | feat(clipboard): g:clipboard="foo" forces the "foo" clipboard tool #33235Deveshi Dwivedi2025-04-03
| |
* | 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 #33279 from zeertzjq/vim-8293574zeertzjq2025-04-03
|\ | | | | vim-patch: zip plugin updates
| * vim-patch:a359c9c: runtime(zip): add *.whl to the list of zip extensionszeertzjq2025-04-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This commits adds the extension *.whl to the list of zip extensions. Wheel (WHL) files are binary distribution files for python packages. Reference: https://packaging.python.org/en/latest/specifications/binary-distribution-format/ fixes: vim/vim#17038 https://github.com/vim/vim/commit/a359c9c25e5c3c1e543fc720223aa7256e6f72cf Co-authored-by: Christian Brabandt <cb@256bit.org>
| * vim-patch:8293574: runtime(doc): update pi_zip.txt with current list of zip ↵zeertzjq2025-04-03
|/ | | | | | | | | | file extensions closes: vim/vim#17037 https://github.com/vim/vim/commit/8293574c8b116382ed6e0c3c709a04406f07cfd5 Co-authored-by: Christian Brabandt <cb@256bit.org>
* fix(events): crash on SIGTSTP (Ctrl-Z) #33258phanium2025-04-02
| | | | | | | | | | Problem: Nvim crashes on receive SIGTSTP (Ctrl-Z) since 4dabeff308222307ede8e74a2bd341713a7f7d81. Solution: * Don't exit on SIGTSTP (not a deadly signal). * Avoid SIGTSTP handler in os/signal.c. Co-authored-by: 27Onion Nebell <zzy20080201@gmail.com>
* fix(highlight): no match highlight during :substitute prompt #33262luukvbaal2025-04-02
| | | | | | Problem: Redrawing during a substitute confirm prompt causes the match highlight to disappear. Solution: Unset `highlight_match` after the prompt has returned. Use global highlight definitions in searchhl_spec.lua.
* vim-patch:9.1.1266: MS-Windows: type conversion warnings (#33264)zeertzjq2025-04-02
| | | | | | | | | | Problem: MS-Windows: type conversion warnings Solution: cast the variables (Yegappan Lakshmanan) closes: vim/vim#17027 https://github.com/vim/vim/commit/7b6add0b4a694d421a1eb9c9017698ccbedde41c Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.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
* | fix(api): nvim_set_keymap() throws error even in pcall() #33228tstsrt2025-04-01
| | | | | | | | | | | | | | | | Problem: When `nvim_set_keymap` tries to overwrite a `<unique>` mapping, it throws an error even when called in `pcall`. Solution: src/nvim/mapping.c:buf_do_map no longer calls `semsg`. Its callers now decide whether to ignore the error, or use `semsg` (not caught)/`api_set_error` (caught by `pcall`).
* | fix(window): crash on negative window height with 'winbar' #33250luukvbaal2025-04-01
| | | | | | | | Problem: Negative window and grid height with 'winbar'. Solution: Clamp the height when subtracting the 'winbar' height.
* | 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.
* | vim-patch:4ac995b: runtime(rust): set formatprg to rustfmt (#33245)zeertzjq2025-04-01
| | | | | | | | | | | | | | closes: vim/vim#16967 https://github.com/vim/vim/commit/4ac995bf9366c6624a0724d19b2226f4c95694b3 Co-authored-by: Konfekt <Konfekt@users.noreply.github.com>
* | fix(display): wrong cursor column with 'concealcursor' = "n" and virt_text ↵luukvbaal2025-04-01
| | | | | | | | | | | | | | (#33218) Problem: Inline virtual text placed in a decor provider callback invalidates `w_virtcol`, which must be valid for `win_line()`. Solution: Call `validate_virtcol()` after "line" decor provider callbacks.
* | fix(move): adjust for concealed lines above topline after scrolling up (#33211)luukvbaal2025-04-01
| | | | | | | | | | | | Problem: Scrolling up does not adjust `w_topline` for concealed lines directly above it, resulting in (non-visual) asymmetry when scrolling up/down. Solution: Adjust `w_topline` for concealed lines after scrolling up.
* | vim-patch:9.1.1265: tests: no tests for typing normal char during completion ↵zeertzjq2025-04-01
|/ | | | | | | | | | | | | | (#33239) Problem: tests: no tests for typing normal char during completion Solution: add a test verifying the default behaviour (see :h popupmenu-completion) related: vim/vim#17019 https://github.com/vim/vim/commit/71f17fdd5f7bb05d78876b4db297824054377363 Co-authored-by: Christian Brabandt <cb@256bit.org> Co-authored-by: Girish Palya <girishji@gmail.com>
* 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.
* test(float): restore border tests (#33222)zeertzjq2025-03-31
|
* vim-patch:649a237: runtime(debversions): Add release name for Debian 15 - ↵zeertzjq2025-03-31
| | | | | | | | | | | duke (#33207) https://lists.debian.org/debian-devel-announce/2025/01/msg00004.html closes: vim/vim#17010 https://github.com/vim/vim/commit/649a237bc886a2b702e95d5d45f661d8db6025f8 Co-authored-by: James McCoy <jamessan@jamessan.com>
* feat(float): 'winborder' "bold" style #33189glepnir2025-03-31
|
* fix(defaults): enable :terminal [[,]] motion in operator-pending mode #33217Ghjuvan Lacambre2025-03-31
| | | This enables y]] to copy a command and its output.
* feat(editor): 'autowriteall' on SIGHUP/SIGQUIT #32843Skoh2025-03-31
| | | | | | | | | | | Problem: Upon receiving a deadly signal, Nvim doesn't write buffers even if the option 'autowriteall' is set. Solution: Write to all writable buffers upon SIGHUP or SIGQUIT (but not SIGTERM), if the option 'autowriteall' is set. Co-authored-by: Justin M. Keyes <justinkz@gmail.com>
* Merge pull request #32440 from fredizzimo/message-attachbfredl2025-03-31
|\ | | | | fix(ui): send multigrid message position and size when the UI is refreshed
| * fix(ui): send multigrid message position and size when the UI is refreshedFred Sundvik2025-03-27
| |
* | fix(treesitter): don't memoize modified headings (#33186)Tan, Long2025-03-31
| | | | | | | | | | Problem: repeated gO in markdown etc. adds extra toc indentation Solution: don't memoize heading table which gets modified
generated by cgit (git 2.34.1) at 2025-07-07 02:10:10 +0000