aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* feat(quickfix): support -q - to read 'errorfile' from stdin (#27303)zeertzjq2024-02-02
| | | Note that this only works when stdin is a pipe.
* vim-patch:9204f39580bdChristian Clason2024-02-02
| | | | | | | | | | | runtime(fortran): update syntax (vim/vim#13953) * runtime (Fortran) update syntax * runtime (Fortran) small fix https://github.com/vim/vim/commit/9204f39580bde807808b352df178fa02b5503a81 Co-authored-by: Ajit-Thakkar <142174202+Ajit-Thakkar@users.noreply.github.com>
* feat(ex_cmds): no error on :lua with {range} and {code} (#27290)luukvbaal2024-02-02
| | | | | | Problem: Erroring when both {range} and {code} are supplied to :lua is inconvenient and may break mappings. Solution: Don't error, ignore {range} and execute {code} when both are supplied.
* refactor(runtime): remove nvimMap and nvimUnmap syntax groups (#27298)zeertzjq2024-02-02
| | | | They are no longer needed as they are covered by vimMap and vimUnmap. Also fix some other mistakes and missing changes.
* Merge pull request #27297 from zeertzjq/vim-e3e3934bb182zeertzjq2024-02-02
|\ | | | | vim-patch:69866449ddb2,e3e3934bb182
| * vim-patch:e3e3934bb182zeertzjq2024-02-02
| | | | | | | | | | | | | | | | | | | | runtime(vim): Update syntax file (vim/vim#13948) Improve string escape sequence and special key matching. https://github.com/vim/vim/commit/e3e3934bb18294b1a5636ed65299d3479f289a8e Co-authored-by: dkearns <dougkearns@gmail.com>
| * vim-patch:69866449ddb2zeertzjq2024-02-02
|/ | | | | | | | | | | | | | | | runtime(vim): Improve keymap file highlighting (vim/vim#13550) - Match :loadkeymap to EOF as a region and contain only allowed items. - Add highlighting for <Char- notation. - add basic syntax highlighting tests https://github.com/vim/vim/commit/69866449ddb20e329f4bc5250312fbfb4a773986 N/A patches: vim-patch:35928ee8f80ea721e92bb856c8ecde2cced46bb9 vim-patch:b5352931b354eb67eb7d223cc09c98dcf1b547b6 Co-authored-by: dkearns <dougkearns@gmail.com>
* Merge pull request #27122 from luukvbaal/signcolbfredl2024-02-01
|\ | | | | fix(column): clear "b_signcols" before moving saved marks
| * fix(column): clear "b_signcols" before moving saved marksLuuk van Baal2024-01-27
| | | | | | | | | | | | Problem: Marks moved by undo may be lost to "b_signcols.count". Solution: Count signs for each undo object separately instead of once for the entire undo.
* | build: various fixesdundargoc2024-02-01
| | | | | | | | | | | | | | - Consistently use the variable CMAKE_BUILD_TYPE to select build type. - Remove broken `doc_html` target. - Remove swap files created by oldtest when cleaning. - Only rerun `lintdoc` if any documentation files has changed.
* | refactor(api): remove some unnecessary HAS_KEY() (#27283)zeertzjq2024-02-01
| | | | | | | | Since keydicts are already zero-initialized, HAS_KEY() isn't needed if the zero-initialized value can satisfy some other condition.
* | vim-patch:c46c21b4ca47Christian Clason2024-02-01
| | | | | | | | | | | | | | | | | | | | | | runtime(netrw): fixing remote file removal via ssh (vim/vim#13942) Make pattern, which retrieves the path component from e.g. `scp://user@host//opt/program/file.ext` non-greedy. https://github.com/vim/vim/commit/c46c21b4ca476c0846a410d7c4d8c6e3e930f167 Co-authored-by: MiguelBarro <45819833+MiguelBarro@users.noreply.github.com>
* | vim-patch:83f627ff42a3Christian Clason2024-02-01
| | | | | | | | | | | | | | | | | | | | | | | | | | runtime(racket): add missing space to b:undo_indent var (vim/vim#13945) This copies commit 2a4862a (fixup! indent: only reset some options when has vim9, 2024-01-31) from https://github.com/benknoble/vim-racket and fixes 26b0176a9 (runtime(racket): undo some indent options only when vim9script is available (vim/vim#13935), 2024-01-30). https://github.com/vim/vim/commit/83f627ff42a3da94db1299493b2cd1133c179850 Co-authored-by: D. Ben Knoble <ben.knoble+github@gmail.com>
* | build(deps): bump luajit to HEAD - 9cc2e42b1Christian Clason2024-02-01
| |
* | feat(api): make nvim_open_win support non-floating windows (#25550)Will Hopkins2024-02-01
| | | | | | | | Adds support to `nvim_open_win` and `nvim_win_set_config` for creating and manipulating split (non-floating) windows.
* | vim-patch:8.2.0085: dead code in builtin functions (#27281)zeertzjq2024-02-01
| | | | | | | | | | | | | | | | Problem: Dead code in builtin functions. Solution: Clean up the code. https://github.com/vim/vim/commit/3d8a513b46b586cb5d2893e7f28c5f51c4dfdc17 Co-authored-by: Bram Moolenaar <Bram@vim.org>
* | vim-patch:8.2.0117: crash when using gettabwinvar() with invalid arguments ↵zeertzjq2024-02-01
| | | | | | | | | | | | | | | | | | | | | | (#27280) Problem: Crash when using gettabwinvar() with invalid arguments. (Yilin Yang) Solution: Use "curtab" if "tp" is NULL. (closes vim/vim#5475) https://github.com/vim/vim/commit/ee93b737aaa7bf65edc7281f429dd89fcf657a6f Co-authored-by: Bram Moolenaar <Bram@vim.org>
* | build: update builtin terminfo (#27272)zeertzjq2024-01-31
| | | | | | | | | | - Update to ncurses 6.4.20230520 - Disable smglp and smgrp for vtpcon and conemu - Add xterm+sl to vtpcon, fix #26880
* | vim-patch:bdb9d9afba97Christian Clason2024-01-31
| | | | | | | | | | | | | | | | | | | | runtime(netrw): Use :exec norm! <leftmouse> before :call mapping in netrw (vim/vim#12180) fixes: vim/vim#12143 https://github.com/vim/vim/commit/bdb9d9afba9769b1cb9c0b320086142d99034c9a Co-authored-by: user202729 <25191436+user202729@users.noreply.github.com>
* | vim-patch:26b0176a98f8Christian Clason2024-01-31
| | | | | | | | | | | | | | | | | | | | | | runtime(racket): undo some indent options only when vim9script is available (vim/vim#13935) This copies commit 64edf95 (indent: only reset some options when has vim9, 2024-01-30) from https://github.com/benknoble/vim-racket. https://github.com/vim/vim/commit/26b0176a98f88acef840d7285e967859eb746c1c Co-authored-by: D. Ben Knoble <ben.knoble+github@gmail.com>
* | fix(statusline): missing offset when showing 'keymap' (#27270)zeertzjq2024-01-31
| |
* | fix(lua): avoid internal error when :luado deletes lines (#27262)zeertzjq2024-01-30
| |
* | vim-patch:9.1.0065: Segfault with CompleteChanged autocommand (#27261)zeertzjq2024-01-30
| | | | | | | | | | | | | | | | | | | | | | Problem: Segfault with CompleteChanged autocommand (markonm ) Solution: Test match->cp_prev for being NULL before accessing it closes: vim/vim#13929 https://github.com/vim/vim/commit/fef66301665027f1801a18d796f74584666f41ef Co-authored-by: Christian Brabandt <cb@256bit.org>
* | fix(gen_help_html): type warnings, spell_ignore_files #27254Jongwook Choi2024-01-29
| | | | | | | | | | - Add type annotations, fix most of the type warnings. - Fix a minor bug on `spell_ignore_files`: nil error when an invalid spelling is found but the file is not ignored.
* | Merge #27246 from justinmk/healthJustin M. Keyes2024-01-29
|\ \
| * | fix(health): "attempt to concatenate nil"Justin M. Keyes2024-01-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: If `neovim` module is not installed, python and ruby healthchecks fail: - ERROR Failed to run healthcheck for "provider.python" plugin. Exception: .../runtime/lua/provider/python/health.lua:348: attempt to concatenate local 'pyname' (a nil value) - ERROR Failed to run healthcheck for "provider.ruby" plugin. Exception: .../runtime/lua/provider/ruby/health.lua:25: attempt to index local 'host' (a nil value) Solution: Check for non-nil.
| * | fix(health): check more "old" filesJustin M. Keyes2024-01-28
| | |
* | | docs: document special labels used in CIdundargoc2024-01-29
| | |
* | | vim-patch:9.1.0061: UX of visual highlighting can be improved (#27256)Evgeni Chasnovski2024-01-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: UX of visual highlighting can be improved Solution: Improve readibility of visual highlighting, by setting better foreground and background colors The default visual highlighting currently is nice in that it overlays the actual syntax highlighting by using a separate distinct background color. However, this can cause hard to read text, because the contrast between the actual syntax element and the background color is way too low. That is an issue, that has been bothering colorschemes authors for quite some time so much, that they are defining the Visual highlighting group to use a separate foreground and background color, so that the syntax highlighting vanishes, but the text remains readable (ref: vim/colorschemesvim/vim#250) So this is an attempt to perform the same fix for the default Visual highlighting and just use a default foreground and background color instead of using reverse. I also removed the hard-coded changes to the Visual highlighting in init_highlight. It's not quite clear to me, why those were there and not added directly to the highlighting_init_<dark|light> struct. closes: vim/vim#13663 related: vim/colorschemes#250 https://github.com/vim/vim/commit/e6d8b4662ddf9356da53f56e363b67b524fd8825 Co-authored-by: Christian Brabandt <cb@256bit.org>
* | | feat(api): add nvim_tabpage_set_win (#27222)Will Hopkins2024-01-29
| | | | | | | | | | | | Allows setting the current window of a non-current tabpage without switching tabpages.
* | | vim-patch:cf8695d48cddzeertzjq2024-01-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | runtime(vim): Highlight string interpolation closes: vim/vim#13923 https://github.com/vim/vim/commit/cf8695d48cdded63043430af5a84185e9614e84c Co-authored-by: thinca <thinca@gmail.com>
* | | vim-patch:21ce159e0561zeertzjq2024-01-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | runtime(vim): Update syntax and ftplugin files (vim/vim#13924) Improve matching of line-continuations and interspersed comments. These are now also matched in multiline syntax command patterns, dictionary literals, and parenthesised expressions and argument lists. https://github.com/vim/vim/commit/21ce159e05615fd139c564b734a4bffc9f3fdc4b Co-authored-by: dkearns <dougkearns@gmail.com>
* | | vim-patch:c79646dfb101zeertzjq2024-01-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | runtime(vim): Update syntax file (vim/vim#13671) Support multiline :syntax commands. Match :syn-cchar option in :syn-{keyword,region}. https://github.com/vim/vim/commit/c79646dfb10126f4ef22734d8713f2352197435e Co-authored-by: dkearns <dougkearns@gmail.com>
* | | vim-patch:71b6d3397649zeertzjq2024-01-29
| | | | | | | | | | | | | | | | | | | | | | | | Update runtime files https://github.com/vim/vim/commit/71b6d3397649fed68ef587aa863fcbdf5fdb057a Co-authored-by: Bram Moolenaar <Bram@vim.org>
* | | feat(extmarks): subpriorities (relative to declaration order) (#27131)Gregory Anders2024-01-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The "priority" field of extmarks can be used to set priorities of extmarks which dictates which highlight group a range will actually have when there are multiple extmarks applied. However, when multiple extmarks have the same priority, the only way to enforce an actual priority is through the order in which the extmarks are set. It is not always possible or desirable to set extmarks in a specific order, however, so we add a new "subpriority" field that explicitly enforces the ordering of extmarks that have the same priority. For now this will be used only to enforce priority of treesitter highlights. A single node in a treesitter tree may match multiple captures, in which case that node will have multiple extmarks set. The order in which captures are returned from the treesitter API is not _necessarily_ in the same order they are defined in a query file, so we use the new subpriority field to force that ordering. For now subpriorites are not documented and are not meant to be used by external code, and it only applies to ephemeral extmarks. We indicate the "private" nature of subpriorities by prefixing the field name with an "_".
* | | fix(jumplist): Ctrl+o, Ctrl+i weird behavior when deleting buffers #25461vE5li2024-01-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: - Navigation is not always symmetric: pressing Ctrl+o n times followed by Ctrl+i n times does not always gets me back to where I started. - Invalid buffers are not skipped by Ctrl+i/o, I have to press Ctrl+i/o multiple times to get to the next/previous buffer. Solution: - Remove all entries of a buffer from the jump list when deleting it. - Don't add a new entry to the jump list if the next buffer to be displayed is already in the jump list. Closes #25365
* | | refactor(lsp): client_hints typo #27250Maria José Solano2024-01-28
| | |
* | | refactor(window.c): add a few more assertions (#27249)zeertzjq2024-01-29
| | |
* | | docs: enforce "treesitter" spelling #27110Jongwook Choi2024-01-28
| | | | | | | | | It's the "tree-sitter" project, but "treesitter" in our code and docs.
* | | test: more tests for nvim_tabpage_get_win (#27248)zeertzjq2024-01-29
| | |
* | | vim-patch:9.1.0060: Recorded register cannot be translated using keytrans() ↵zeertzjq2024-01-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (#27247) Problem: Recorded register cannot be translated using keytrans() when it involves character search (iddqd505) Solution: Record a K_IGNORE instead of a K_NOP (zeertzjq) related: vim/vim#13916 closes: vim/vim#13925 https://github.com/vim/vim/commit/bf321806bf44d59f108fd7e5a0eaead04682701d
* | | docs: .git-blame-ignore-revs #26397Justin M. Keyes2024-01-28
|/ /
* | docs: update FAQ URLs #27236Justin M. Keyes2024-01-28
| |
* | docs: include backtrace for bug-crash #27065Jongwook Choi2024-01-28
| | | | | | | | | | | | | | | | | | | | | | | | Github Issue template: - Add pointers to |dev-tools-backtrace|. - Add pointers to CONTRIBUTING.md (Reporting Problems), which includes additional helpful instructions for issue reporting. - Search existing issues: include label `bug-crash` as well as `bug`. CONTRIBUTING.md: - Fix broken link on "stacktrace" after moving to help from wiki.
* | build(docs): separate lint job to validate vimdoc #27227Jongwook Choi2024-01-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Summary: Separate the lint job (`make lintdoc`) to validate runtime/doc, it is no longer as a part of functionaltest (help_spec). Build (cmake) and CI: - `make lintdoc`: validate vimdoc files and test-generate HTML docs. CI will run this as a part of the "docs" workflow. - `scripts/lintdoc.lua` is added as an entry point (executable script) for validating vimdoc files. scripts/gen_help_html.lua: - Move the tests for validating docs and generating HTMLs from `help_spec.lua` to `gen_help_html`. Added: - `gen_help_html.run_validate()`. - `gen_help_html.test_gen()`. - Do not hard-code `help_dir` to `build/runtime/doc`, but resolve from `$VIMRUNTIME`. Therefore, the `make lintdoc` job will check doc files on `./runtime/doc`, not on `./build/runtime/doc`. - Add type annotations for gen_help_html.
* | docs: explain why TUI is reinitialized on resume (#27177)Gregory Anders2024-01-28
| |
* | test(lua/snippet_spec): wait for completion menu (#27243)zeertzjq2024-01-28
| | | | | | | | This fixes the flakiness caused by typing a completion menu key when the completion menu hasn't showed up.
* | test(tui): add & improve tests for terminal queries (#27219)Gregory Anders2024-01-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problems: 1. The test case for querying truecolor support did not check which capabilities were queried 2. The test case for querying truecolor support checked `&termguicolors` in the Nvim test runner, not the child Nvim in the the embedded terminal 3. The test case for querying truecolor support did not actually respond to the XTGETTCAP requests. `'termguicolors'` is still enabled even without responding to this query because libvterm understands and responds to the DECRQSS request, but it is still good to respond to the query explicitly instead of depending on hidden libvterm behavior 4. No test case exists at all for OSC 52 Solution: Fix all of the problems listed above.
* | Merge pull request #24704 from seandewar/cmdwin-madnessSean Dewar2024-01-28
|\ \ | | | | | | vim-patch:9.1.{0047,0048,0049}: fun cmdwin fixes
| * | vim-patch:9.1.0049: Make "[Command Line]" a special buffer nameSean Dewar2024-01-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: E95 is possible if a buffer called "[Command Line]" already exists when opening the cmdwin. This can also happen if the cmdwin's buffer could not be deleted when closing. Solution: Un-name the cmdwin buffer, and give it a special name instead, similar to what's done for quickfix buffers and for unnamed prompt and scratch buffers. As a result, BufFilePre/Post are no longer fired when opening the cmdwin. Add a "command" key to the dictionary returned by getbufinfo() to differentiate the cmdwin buffer instead. (Sean Dewar) Cherry-pick test_normal changes from v9.0.0954. https://github.com/vim/vim/commit/1fb41032060df09ca2640dc49541f11062f6dfaa
generated by cgit (git 2.34.1) at 2025-06-24 11:24:27 +0000