aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
| * | fix(filetype): don't pass empty string to detect (#20766)Christian Clason2022-10-21
| | | | | | | | | | | | | | | Problem: `*.db` files use empty string as default filetype, which is inconsistent with the rest of the code which uses `nil` instead. Solution: don't pass a default empty string
| * | vim-patch: bump VIM_VERSION from 8.0 => 8.1 #20762Justin M. Keyes2022-10-21
| |/ | | | | | | There are 6 remaining 8.0.x patches, tracked in: https://github.com/neovim/neovim/issues/5431
| * vim-patch:9.0.0806: 'langmap' works differently when there are modifiers ↵zeertzjq2022-10-21
| | | | | | | | | | | | | | | | (#20754) Problem: 'langmap' works differently when there are modifiers. Solution: Only apply 'langmap' to a character where modifiers have no effect. (closes vim/vim#11395, closes vim/vim#11404) https://github.com/vim/vim/commit/49660f5139d3fd55326a54eadf6bb31a3ffec2bf
| * vim-patch:9.0.0808: jsonnet filetype detection has a typo (#20753)Christian Clason2022-10-20
| | | | | | | | | | Problem: jsonnet filetype detection has a typo. Solution: Change "libjsonnet" to "libsonnet". (Maxime Brunet, closes vim/vim#11412) https://github.com/vim/vim/commit/6c8bc37a1083d17447156592f6f52da2d40b4855
| * Merge pull request #20748 from zeertzjq/vim-9.0.0804zeertzjq2022-10-20
| |\ | | | | | | vim-patch:partial:8.2.0418,9.0.0804: crash when trying to divide a number by -1
| | * vim-patch:9.0.0804: crash when trying to divide a number by -1zeertzjq2022-10-20
| | | | | | | | | | | | | | | | | | Problem: Crash when trying to divice the largest negative number by -1. Solution: Handle this case specifically. https://github.com/vim/vim/commit/cdef1cefa2a440911c727558562f83ed9b00e16b
| | * vim-patch:partial:8.2.0418: code in eval.c not sufficiently covered by testszeertzjq2022-10-20
| |/ | | | | | | | | | | | | | | | | | | Problem: Code in eval.c not sufficiently covered by tests. Solution: Add more tests. (Yegappan Lakshmanan, closes vim/vim#5815) https://github.com/vim/vim/commit/8b633135106dda8605463b780573c45b00c22afe Only port test_expr.vim and the first hunk of test_cmdline.vim. Add missing test from patch 7.4.1755. Cherry-pick test_expr.vim change from patch 8.2.2060.
| * docs: update vimdoc parser #20747Justin M. Keyes2022-10-20
| | | | | | | | | | | | | | | | | | Remove the user-manual ToC from help.txt, because: 1. it duplicates usr_toc.txt 2. it is not what most readers are looking for in the main help page. fix https://github.com/neovim/tree-sitter-vimdoc/issues/49 fix https://github.com/neovim/tree-sitter-vimdoc/issues/50 fix https://github.com/neovim/tree-sitter-vimdoc/issues/51
| * fix(build): duplicate version string "v0.8.0-v0.8.0" #20578dundargoc2022-10-20
| | | | | | | | | | | | | | | | | | | | - Prevent duplicate version strings such as v0.8.0-v0.8.0. - Change the format for git releases from v0.9.0-dev-67-g625ba79be to v0.9.0-dev-67+g625ba79be. Nvim versions are now: release : v0.9.0 prerelease without git info: v0.9.0-dev prerelease with git info : v0.9.0-dev-67+g625ba79be
| * fix(docs-html): misaligned tabs after conceal #20690Yee Cheng Chin2022-10-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: `gen_help_html.lua` does not properly handle tab characters after "concealed" text (tags, taglinks, codespans). This causes misaligned layout in "old" (preformatted) docs. For text like `*tag*`, |tag_link|, and `code_span`, Vim hides the "*", "|", "`" characters, but Vim still counts those characters for "virtual column" when a tab character follows it. So if you have a tag of say 6 characters long, those two concealed character would lead to the tab character after it start at column 8. gen_help_html.lua doesn't account for that which leads to formatting flaws in the generated output. Solution: Add two spaces after concealed nodes that are followed by a tab char.
| * docs(news): mention 'splitkeep' #20744zeertzjq2022-10-20
| |
| * vim-patch:9.0.0798: clang format configuration files are not recognized (#20741)ObserverOfTime2022-10-19
| | | | | | | | | | | | Problem: Clang format configuration files are not recognized. Solution: Use yaml for Clang format configuration files. (Marwin Glaser, closes vim/vim#11398) https://github.com/vim/vim/commit/3c708c43908ba44f075bbaa7daf584c6b46d9723
| * vim-patch:9.0.0739: mouse column not correctly used for popup_setpos (#20729)zeertzjq2022-10-19
| | | | | | | | | | | | | | | | Problem: Mouse column not correctly used for popup_setpos. Solution: Adjust off-by-one error and handle Visual line selection properly. (Yee Cheng Chin, closes vim/vim#11356) https://github.com/vim/vim/commit/17822c507c03d509037c9ee5eee5cfbb201b3f01 The test_termcodes.vim test cannot be used. Use a Lua test instead.
| * revert: "oldtests: wait 200ms on mac for timer test" (#20728)zeertzjq2022-10-19
| | | | | | This reverts commit 3bad76008e1c98724eca7d986a6340eff1de8193.
| * Merge pull request #20727 from zeertzjq/vim-9.0.0789zeertzjq2022-10-19
| |\ | | | | | | vim-patch:9.0.{0789,0790}
| | * vim-patch:9.0.0790: test for dummy buffer does not always produce the E86 errorzeertzjq2022-10-19
| | | | | | | | | | | | | | | | | | Problem: Test for dummy buffer does not always produce the E86 error. Solution: Do not check if the error is produced. https://github.com/vim/vim/commit/53c5c9f50ca68d3ed559eebb2c5f7d23f39a768c
| | * vim-patch:9.0.0789: dummy buffer ends up in a windowzeertzjq2022-10-19
| |/ | | | | | | | | | | Problem: Dummy buffer ends up in a window. Solution: Disallow navigating to a dummy buffer. https://github.com/vim/vim/commit/8f3c3c6cd044e3b5bf08dbfa3b3f04bb3f711bad
| * vim-patch:9.0.0788: ModeChanged autocmd not executed when Visual ends with ↵zeertzjq2022-10-19
| | | | | | | | | | | | | | | | | | | | CTRL-C (#20722) Problem: ModeChanged autocmd not executed when Visual mode is ended with CTRL-C. Solution: Do not trigger the autocmd when got_int is set. (closes vim/vim#11394) https://github.com/vim/vim/commit/61c4b04799bf114cadc3bbf212ae8b2ad22a6980 Cherry-pick removal of cmdwin feature check from patch 9.0.0663.
| * refactor(window.c): reduce scope of locals (#20301)Lewis Russell2022-10-18
| |
| * vim-patch:9.0.0779: lsl and lm3 file extensions are not recognized (#20704)Christian Clason2022-10-18
| | | | | | | | | | Problem: lsl and lm3 file extensions are not recognized. Solution: Add *.lsl and *.lm3 patterns. (Doug Kearns, closes vim/vim#11384) https://github.com/vim/vim/commit/4ac8e7948cb3e07bc4598ede8b274891d14dfa7c
| * fix(highlight): link more treesitter groups by default (#20711)Christian Clason2022-10-18
| | | | | | | | | | | | | | | | | | | | | | Problem: Captures used by bundled parsers are not highlighted by default Solution: Add links to default groups A link is added for a capture if * there is a default group of the same name (e.g., `@tag` -> `Tag`) * it's used in a bundled query and doesn't have a reasonable fallback (e.g., `@text.literal`) Also add all linked groups to the treesitter docs.
| * feat(docs): update parser, HTML gen #20720Justin M. Keyes2022-10-18
| | | | | | | | | | | | | | | | | | | | Note: although the tolerance in help_spec.lua increased, the actual error count with the new parser decreased by about 20%. The difference is that the old ignore_parse_error() ignored many more errors with the old parser. fix https://github.com/neovim/tree-sitter-vimdoc/issues/37 fix https://github.com/neovim/tree-sitter-vimdoc/issues/44 fix https://github.com/neovim/tree-sitter-vimdoc/issues/47
| * vim-patch:9.0.0786: user command does not get number from :tab modifier (#20716)zeertzjq2022-10-18
| | | | | | | | | | Problem: User command does not get number from :tab modifier. Solution: Include the number. (closes vim/vim#11393, closes vim/vim#6901) https://github.com/vim/vim/commit/208567e9d744ef7b89bed1f62e951ae4ee2f6f5f
| * fix(intro): omit patch version in ":help news" item #20713zeertzjq2022-10-18
| | | | | | | | Because maintenance releases share the same news.txt as the last non-maintenance release.
| * ci: add reviewers based on labels (#20703)dundargoc2022-10-18
| |
| * fix(qflist): avoid read of uninitialized memory (#20709)Mahmoud Al-Qudsi2022-10-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If the call to `qf_setup_state()` in `qf_init_ext()` fails, control flow jumps to label `qf_init_end` where a call to `qf_update_buffer()` is made with `old_last` as a function call argument. Prior to this patch, `old_last` would not yet have been initialized to its default value of `NULL`, resulting in `qf_update_buffer()` attempting to compare against its uninitialized value (quickfix.c:3882) then later forwarding it to `qf_fill_buffer()` where the address is dereferenced and repeatedly read from/ written to for performing core qflist operations. Depending on what the default value of `old_last` was, the results may range from a best case scenario of neovim terminating with SIGSEGV from an attempt to dereference an invalid pointer (quickfix.c:4056) to memory corruption if it contained some other value that results in `qfp` being initialized from `old_last->qf_next` (after which it is subsequently written to and read from in a fairly arbitrary fashion). Though extremely unlikely, it's possible for there to be security considerations as a user can ensure that the next call to `qf_setup_state()` fails. This patch ensures that `old_last` is NULL-assigned before control flow jumps to `qf_init_end`. Closes #20639.
| * ci: bump ubuntu and macos to latest stable versions (#20479)dundargoc2022-10-17
| |
| * vim-patch:9.0.0782: OpenVPN files are not recognized (#20702)Christian Clason2022-10-17
| | | | | | | | | | Problem: OpenVPN files are not recognized. Solution: Add patterns for OpenVPN files. (closes vim/vim#11391) https://github.com/vim/vim/commit/4bf67ec52e938a3edaa4f452adab42a57505f940
| * ci: add cirrus to isCI function to skip tests (#20526)dundargoc2022-10-17
| | | | | | | | The environment variable CIRRUS_CI is manually passed to RunTests.cmake as it doesn't get passed when using cmake script mode.
| * fix(runtime): use `g:terminal_color_{0-15}` in colorschemes (#20637)C.D. MacEachern2022-10-17
| |
| * Merge pull request #20685 from luukvbaal/scrollzeertzjq2022-10-17
| |\ | | | | | | fix: 'scroll' is not set correctly for floats with 'splitkeep'
| | * test: add a test for #20684zeertzjq2022-10-17
| | |
| | * fix: 'scroll' is not set correctly for floats with 'splitkeep'Luuk van Baal2022-10-17
| |/ | | | | | | | | | | | | | | | | vim-patch:9.0.0780: 'scroll' value computed in unexpected location Problem: 'scroll' value computed in unexpected location. Solution: Compute 'scroll' when the window height is changed. (Luuk van Baal, closes vim/vim#11387) https://github.com/vim/vim/commit/a1a46da87d91cfbf46866627b3e66a757145e8c3
| * feat(api): nvim_select_popupmenu_item support cmdline pum (#20652)zeertzjq2022-10-17
| |
| * fix(man): handle absolute paths as `:Man` targets (#20624)Mahmoud Al-Qudsi2022-10-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * fix(man): handle absolute paths as :Man targets Previously, attempting to provide `:Man` with an absolute path as the name would cause neovim to return the following error: ``` Error detected while processing command line: /usr/local/share/nvim/runtime/lua/man.lua:690: /usr/local/share/nvim/runtime/lua/man.lua:683: Vim:E426: tag not found: nil(nil) Press ENTER or type command to continue ``` ..because it would try to validate the existence of a man page for the provided name by executing `man -w /some/path` which (on at least some Linux machines [0]) returns `/some/path` instead of the path to the nroff files that would be formatted to satisfy the man(1) lookup. While man pages are not normally named after absolute paths, users shouldn't be blamed for trying. Given such a name/path, neovim would **not** complain that the path didn't have a corresponding man file but would error out when trying to call the tag function for the null-propagated name-and-section `nil(nil)`. (The same underlying error existed before this function was ported to lua, but did not exhibit the lua-specific `nil(nil)` name; instead a tag lookup for `()` would fail and error out.) With this patch, we detect the case where `man -w ...` returns the same value as the provided name to not only prevent invoking the tag function for a non-existent/malformed name+sect but also to properly report the non-existence of a man page for the provided lookup (the absolute path). While man(1) can be used to directly read an nroff-formatted document via `man /path/to/nroff.doc`, `:Man /path/to/nroff.doc` never supported this behavior so no functionality is lost in case the provided path _was_ an nroff file. [0]: `man -w /absolute/path` returning `/absolute/path` observed on an Ubuntu 18.04 installation. * test: add regression test for #20624 Add a functional test to `man_spec.lua` to check for a regression for #20624 by first obtaining an absolute path to a random file and materializing it to disk, then attempting to query `:Man` for an entry by that same name/path. The test passes if nvim correctly reports that there is no man page correspending to the provided name/path and fails if any other error (or no error) is shown.
| * Merge pull request #20665 from lewis6991/fix/decor_redrawLewis Russell2022-10-17
| |\
| | * fix(decoration): call providers in win_update() earlierLewis Russell2022-10-15
| | | | | | | | | | | | Fixes #20651
| * | feat(runtime)!: remove filetype.vim (#20428)Christian Clason2022-10-17
| | | | | | | | | | | | | | | | | | Made obsolete by now graduated `filetype.lua` (enabled by default). Note that changes or additions to the filetype detection still need to be made through a PR to vim/vim as we port the _logic_ as well as tests.
| * | vim-patch:3c053a1a5ad2 (#20679)Christian Clason2022-10-17
| | | | | | | | | | | | Update runtime files https://github.com/vim/vim/commit/3c053a1a5ad2a3c924929e11f2b9af20a8b901e2
| * | vim-patch:9.0.0771: cannot always tell the difference beween tex and … ↵Jonas Strittmatter2022-10-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (#20687) vim-patch:9.0.0771: cannot always tell the difference beween tex and rexx files Problem: Cannot always tell the difference beween tex and rexx files. Solution: Recognize tex by a leading backslash. (Martin Tournoij, closes vim/vim#11380) https://github.com/vim/vim/commit/bd053f894b0d7652928201faa68c53d1ce2acdc5
| * | docs: "supported platforms" matrix #19615dundargoc2022-10-16
| | | | | | | | | | | | | | | | | | Inspired by libuv's own SUPPORTED_PLATFORMS.md: https://github.com/libuv/libuv/blob/v1.x/ https://neovim.io/doc/user/support.html
| * | fix(lsp): reporting bogus capabilities in CodeActionKind #20678David Hotham2022-10-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: LSP client provides bogus capabilities in CodeActionKind. LSP logs show this in the "initialize" message: codeActionKind = { valueSet = { "Empty", "QuickFix", "Refactor", "RefactorExtract", "RefactorInline", "RefactorRewrite", "Source", "SourceOrganizeImports", "", "quickfix", "refactor", "refactor.extract", "refactor.inline", "refactor.rewrite", "source", "source.organizeImports" } Solution: Only the values from the CodeActionKind table should be presented, not also the keys. fix #20657
| * | feat: mention ":help news" in intro #20674Gregory Anders2022-10-16
| | |
| * | Merge pull request #20677 from zeertzjq/vim-9.0.0761zeertzjq2022-10-16
| |\ \ | | | | | | | | vim-patch:9.0.{0761,0762,0764}: 'lispoptions'
| | * | vim-patch:9.0.0764: indent and option tests failzeertzjq2022-10-16
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Indent and option tests fail. Solution: Change OP_INDENT. Add entry to options test table. https://github.com/vim/vim/commit/c8b673557390e5cd20bc0a4c2786d0db1d77a24c
| | * | vim-patch:9.0.0761: cannot use 'indentexpr' for Lisp indentingzeertzjq2022-10-16
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Cannot use 'indentexpr' for Lisp indenting. Solution: Add the 'lispoptions' option. https://github.com/vim/vim/commit/49846fb1a31de99f49d6a7e70efe685197423c84 vim-patch:9.0.0762: build failure Problem: Build failure. Solution: Add missing change. https://github.com/vim/vim/commit/4b082c4bd05f504fda1acaa9d28fca55a2d04857
| * / vim-patch:9.0.0765: with a Visual block a put command column may go negative ↵zeertzjq2022-10-16
| |/ | | | | | | | | | | | | (#20676) Problem: With a Visual block a put command column may go negative. Solution: Check that the column does not become negative. https://github.com/vim/vim/commit/36343ae0fb7247e060abfd35fb8e4337b33abb4b
| * refactor(drawscreen.c): reduce scopes of locals (#20668)Lewis Russell2022-10-15
| |
| * Merge pull request #20140 from dundargoc/refactor/char_u/12bfredl2022-10-15
| |\ | | | | | | refactor: replace char_u with char 12: remove `STRLEN` part 2
| | * refactor: replace char_u with charDundar Göc2022-10-15
| | | | | | | | | | | | Work on https://github.com/neovim/neovim/issues/459
generated by cgit (git 2.34.1) at 2025-06-23 23:10:25 +0000