aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
| | * | vim-patch:8.2.3202: Vim9: tests are only executed for legacy scriptzeertzjq2023-06-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Vim9: tests are only executed for legacy script. Solution: Run more tests also for Vim9 script. Fix uncovered problems. https://github.com/vim/vim/commit/5dd839ce20466eea52e59ecf86456f1ab370d2bd Co-authored-by: Bram Moolenaar <Bram@vim.org>
| | * | vim-patch:8.2.3191: Vim9: not enough code is testedzeertzjq2023-06-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Vim9: not enough code is tested. Solution: Use CheckLegacyAndVim9Success() in more places. Fix uncovered problems. https://github.com/vim/vim/commit/63cb6567f0153c35dc75cbc09039ff5d0a7b60e3 Co-authored-by: Bram Moolenaar <Bram@vim.org>
| | * | vim-patch:8.2.2533: Vim9: cannot use a range with :unletzeertzjq2023-06-12
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | Problem: Vim9: cannot use a range with :unlet. Solution: Implement ISN_UNLETRANGE. https://github.com/vim/vim/commit/5b5ae29bd3d7b832b6f15320430f7f191e0abd1f Co-authored-by: Bram Moolenaar <Bram@vim.org>
| * | Merge pull request #23995 from zeertzjq/vim-8.2.1524zeertzjq2023-06-12
| |\ \ | | | | | | | | vim-patch:8.2.{1524,2948,2949}: Float to String conversion
| | * | test(unit/eval/typval_spec): adjust for Float to String conversionSean Dewar2023-06-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adjust relevant Lua tests. Refactor testing logic for tv_get_string_* functions into test_string_fn(). Note that vim_snprintf(), which is used for stringifying floats, always calls xfree(tofree), even if tofree is NULL, so we need to expect that in the alloc log.
| | * | vim-patch:8.2.2949: tests failing because no error for float to string ↵zeertzjq2023-06-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | conversion Problem: Tests failing because there is no error for float to string conversion. Solution: Change the check for failure to check for correct result. Make some conversions strict in Vim9 script. https://github.com/vim/vim/commit/3cfa5b16b06bcc034f6de77070fa779d698ab5e9 Co-authored-by: Bram Moolenaar <Bram@vim.org>
| | * | test(unit/eval/typval_spec): don't dereference NULL last_msg_histSean Dewar2023-06-12
| | | | | | | | | | | | | | | | | | | | If last_msg_hist is NULL, check_emsg will cause the running test process to SIGSEGV from trying to access the msg member.
| | * | vim-patch:8.2.2948: substitute() accepts a number but not a float expressionSean Dewar2023-06-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Substitute() accepts a number but not a float expression. Solution: Also accept a float. (closes vim/vim#8331) https://github.com/vim/vim/commit/7a2217bedd223df4c8bbebe731bf0b5fe8532533 Vim9script is N/A. No need to port the strict argument and tv_get_string_buf_chk_strict(), as it's only used for Vim9script. Like the patch, use vim_snprintf over snprintf, as the "%g" specifier in snprintf removes the ".0" from integer floats. This means similiar to numbers, floats are (mostly) convertable to strings. Co-authored-by: Bram Moolenaar <Bram@vim.org>
| | * | vim-patch:8.2.1524: no longer get an error for string concatenation with floatSean Dewar2023-06-12
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: No longer get an error for string concatenation with float. (Tsuyoshi Cho) Solution: Only convert float for Vim9 script. (closes vim/vim#6787) https://github.com/vim/vim/commit/2e0866128b6266829a7f38733d5188bc4ec68745 Vim9script is N/A. Required for v8.2.2949. Co-authored-by: Bram Moolenaar <Bram@vim.org>
| * | test(old): reorder test_substitute.vim to match upstream (#23994)zeertzjq2023-06-12
| | |
| * | Merge #23954 vim.version() returns Version objectJustin M. Keyes2023-06-11
| |\ \
| | * | feat: tostring(vim.version())Justin M. Keyes2023-06-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: tostring(vim.version()) returns "table: 0x…". Solution: Modify vim.version() to return a string prerelease instead of a boolean. Fix #23863
| | * | feat: vim.version() returns a Version objectGianmaria Bajo2023-06-12
| | | | | | | | | | | | | | | | | | | | | | | | - vim.version() returns a Version object. Makes it printable and removes the need of workarounds when passing it to other vim.version methods.
| * | | docs: fix vim.tbl_get type annotations #23992Stanislav Asunkin2023-06-11
| |/ /
| * | refactor: remove WINGUI_URLJustin M. Keyes2023-06-12
| | | | | | | | | | | | nvim-qt was removed in 0370e4def0c0328f8cd09f02c1ca82ed491ecb9a
| * | feat: report "build" in vim.version() #23925treatybreaker2023-06-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Nvim version string typically has a "build" component but vim.version() doesn't report it. Solution: Add the "build" field to vim.version(). Closes #23863
| * | docs: semantic token methods in :h lsp-method #23991jdrouhard2023-06-11
| | |
| * | refactor(treesitter): use npcall in _query_linter.lua #23985Stephan Seitz2023-06-11
| | |
| * | fix(remote): restore previous --remote-expr output formatting (#23988)zeertzjq2023-06-11
| | | | | | | | | | | | - Use tostring() as that's what print() uses internally. - Do not append trailing new line.
| * | Merge pull request #23968 from figsoda/bundleMatthieu Coudron2023-06-11
| |\ \ | | | | | | | | build(nix): use the correct versions of the bundled treesitter parsers
| | * | build(nix): use the correct versions of the bundled treesitter parsersfigsoda2023-06-09
| | | |
| | * | build(nix): update flake.lockfigsoda2023-06-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Flake lock file updates: • Updated input 'flake-utils': 'github:numtide/flake-utils/5aed5285a952e0b949eb3ba02c12fa4fcfef535f' (2022-11-02) → 'github:numtide/flake-utils/a1720a10a6cfe8234c0e93907ffe81be440f4cef' (2023-05-31) • Added input 'flake-utils/systems': 'github:nix-systems/default/da67096a3b9bf56a91d16901293e51ba5b49a27e' (2023-04-09) • Updated input 'nixpkgs': 'github:nixos/nixpkgs/abe7316dd51a313ce528972b104f4f04f56eefc4' (2023-04-14) → 'github:nixos/nixpkgs/a64b73e07d4aa65cfcbda29ecf78eaf9e72e44bd' (2023-06-08)
| * | | vim-patch:f1dcd14fc5d4 (#23986)zeertzjq2023-06-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Update runtime files https://github.com/vim/vim/commit/f1dcd14fc5d4370476cd82895a4479ca2d252e54 :autocmd-block is N/A (Vim9 script) Co-authored-by: Bram Moolenaar <Bram@vim.org>
| * | | vim-patch:10e8ff9b2607 (#23977)Sean Dewar2023-06-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Update runtime files https://github.com/vim/vim/commit/10e8ff9b26078994cae57c2422b145d37aaf714e Also: - fix a missing `<` in builtin.txt. - edit `:function` `{name}` wording to match the change made for the docs above by Justin in #10619. - link to `*vimrc*` rather than `*init.vim*` in repeat.txt change (as `init.lua` may also be used). Co-authored-by: Bram Moolenaar <Bram@vim.org>
| * | | feat(lsp): add handlers for inlay hints (#23736)Chinmay Dalal2023-06-11
| | | | | | | | | | | | initial support; public API left for a follow-up PR
| * | | fix(remote): make --remote-expr print to stdout (#23980)zeertzjq2023-06-11
| | | |
| * | | fix(helptags): make multibyte help tags work properly (#23975)zeertzjq2023-06-11
| | | |
| * | | vim-patch:9.0.1626: Visual area not shown when using 'showbreak' (#23978)zeertzjq2023-06-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Visual area not shown when using 'showbreak' and start of line is not visible. (Jaehwang Jung) Solution: Adjust "fromcol" for the space taken by 'showbreak'. (closes vim/vim#12514) https://github.com/vim/vim/commit/f578ca2c8f36b61ac3301fe8b59a8473c964cdc2 Co-authored-by: Bram Moolenaar <Bram@vim.org>
| * | | feat(lua): use callable table as iterator in vim.iter (#23957)Mathias Fußenegger2023-06-10
| | | | | | | | | | | | | | | | A table passed to `vim.iter` can be a class instance with a `__call` implementation for the iterator protocol.
| * | | fix(lsp): use percentage format on lsp.status (#23971)Raphael2023-06-10
| | | |
| * | | ci: add runner image version to cache keydundargoc2023-06-10
| | | | | | | | | | | | | | | | This will ensure the cache isn't used when an image upgrade changes the compiler version, causing the build to fail.
| * | | test: more tests for nvim_{set,del}_keymap with abbreviation (#23970)zeertzjq2023-06-10
| | | |
| * | | docs: fix typos (#23917)Jonas Strittmatter2023-06-10
| | | |
| * | | vim-patch:9.0.1622: filetype name t32 is a bit obscure (#23967)Christian Clason2023-06-09
| |/ / | | | | | | | | | | | | | | | | | | | | | Problem: Filetype name t32 is a bit obscure. Solution: Rename t32 to trace32. (Christoph Sax, closes vim/vim#12512) https://github.com/vim/vim/commit/740df76c90ee2c421ab7852b7ff2835aa0af782a Co-authored-by: Christoph Sax <christoph.sax@mailbox.org>
| * | Merge pull request #23803 from bfredl/luaabbrbfredl2023-06-09
| |\ \ | | | | | | | | feat(api): support abbreviations in nvim_set_keymap
| | * | feat(api): support abbreviations in nvim_set_keymapbfredl2023-06-09
| |/ / | | | | | | | | | closes #19198
| * | vim-patch:9.0.1621: FILETYPE_FILE is defined to the same value multiple ↵zeertzjq2023-06-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | times (#23965) Problem: FILETYPE_FILE is defined to the same value multiple times. Same for a few similar macros. Solution: Define FILETYPE_FILE and others in feature.h only https://github.com/vim/vim/commit/c81dfaa69ceec9f6b88caf1dcdf2f859d4fcae47 Co-authored-by: Bram Moolenaar <Bram@vim.org>
| * | vim-patch:9.0.1617: charidx() result is not consistent with byteidx() (#23963)zeertzjq2023-06-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: charidx() and utf16idx() result is not consistent with byteidx(). Solution: When the index is equal to the length of the text return the lenght of the text instead of -1. (Yegappan Lakshmanan, closes vim/vim#12503) https://github.com/vim/vim/commit/577922b917e48285a7a312daf7b5bbc6e272939c Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
| * | feat(lsp)!: add vim.lsp.status, client.progress and promote ↵Mathias Fußenegger2023-06-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | LspProgressUpdate (#23958) `client.messages` could grow unbounded because the default handler only added new messages, never removing them. A user either had to consume the messages by calling `vim.lsp.util.get_progress_messages` or by manually removing them from `client.messages.progress`. If they didn't do that, using LSP effectively leaked memory. To fix this, this deprecates the `messages` property and instead adds a `progress` ring buffer that only keeps at most 50 messages. In addition it deprecates `vim.lsp.util.get_progress_messages` in favour of a new `vim.lsp.status()` and also promotes the `LspProgressUpdate` user autocmd to a regular autocmd to allow users to pattern match on the progress kind. Also closes https://github.com/neovim/neovim/pull/20327
| * | vim-patch:9.0.1620: Nix files are not recognized from the hashbang line (#23961)Christian Clason2023-06-09
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Nix files are not recognized from the hashbang line. Solution: Add a hashbang check. (issue vim/vim#12507) https://github.com/vim/vim/commit/19548c6a742d954ecd0b50b0680c37cc6ced7473 Co-authored-by: Bram Moolenaar <Bram@vim.org>
| * | vim-patch:9.0.1618: Trace32 files are not recognized (#23960)Christian Clason2023-06-08
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Trace32 files are not recognized. Solution: Add patterns for the t32 filetype. (Christoph Sax, closes vim/vim#12505) https://github.com/vim/vim/commit/7fbcee6f928356f1c205a4dfa67c1d542f743b92 Co-authored-by: Christoph Sax <christoph.sax@mailbox.org>
| * | feat(lua): add ringbuffer (#22894)Mathias Fußenegger2023-06-08
| | | | | | | | | https://en.wikipedia.org/wiki/Circular_buffer
| * | vim-patch:9.0.1616: quickfix text field is truncated (#23951)zeertzjq2023-06-08
| | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Quickfix text field is truncated. Solution: Fix output of text field after pattern field in quickfix buffer. (Shane Harper, closes vim/vim#12498) https://github.com/vim/vim/commit/5bf042810b19a627eda2f170624a0cfd7b4f6ed6 Co-authored-by: Shane Harper <shane@shaneharper.net>
| * | vim-patch:9.0.1615: URL shortcut files are not recognized (#23950)Christian Clason2023-06-07
| | | | | | | | | | | | | | | | | | | | | | | | Problem: URL shortcut files are not recognized. Solution: Add a pattern for URL shortcut files. (closes vim/vim#12474) https://github.com/vim/vim/commit/cdb7b4c50826df254d2e5ba8abd211e49b7a9784 Co-authored-by: ObserverOfTime <chronobserver@disroot.org>
| * | feat(lua): add `vim.system()`Lewis Russell2023-06-07
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | feat(lua): add vim.system() Problem: Handling system commands in Lua is tedious and error-prone: - vim.fn.jobstart() is vimscript and comes with all limitations attached to typval. - vim.loop.spawn is too low level Solution: Add vim.system(). Partly inspired by Python's subprocess module Does not expose any libuv objects.
| * | fix(lsp): reduce diagnostics and add more types (#23948)Lewis Russell2023-06-07
| | |
| * | feat(diff): grouping optimization for linematch algorithmJonathon2023-06-07
| | |
| * | feat(scripts): add lsp_types.lua (#23750)max3975742023-06-07
| | |
| * | refactor(options): use slash separator for `option_get_valid_types()` (#23945)Famiu Haque2023-06-07
| | | | | | | | | | | | | | | | | | `option_get_valid_types()` currently uses a comma separator for multi-type options which does not fit well with the changed error message for invalid option value type. A slash seperator is much more suited for its current use-case.
| * | Merge pull request #23943 from zeertzjq/autocmd-fnamezeertzjq2023-06-07
| |\ \ | | | | | | | | fix(events): don't expand non-file as file name