aboutsummaryrefslogtreecommitdiff
path: root/runtime
Commit message (Collapse)AuthorAge
...
| * feat(lsp): completion opts support custom item conversion (#30060)glepnir2024-08-22
| | | | | | | | | | | | | | Problem: Some items of completion results include function signatures that can cause the pum to be very long when a function has many params, because pum scales with the longest word/abbr. Solution: add custom covert function that can customise abbr to remove params.
| * fix(lsp): suppress completion request if completion is active (#30028)glepnir2024-08-22
| | | | | | | | | | | | | | Problem: the autotrigger mechanism could fire completion requests despite completion already being active from another completion mechanism or manual trigger Solution: add a condition to avoid an additional request.
| * vim-patch:bc29ea6: runtime(zip): simplify condition to detect MS-Windows ↵zeertzjq2024-08-22
| | | | | | | | | | | | | | | | | | (#30115) related: vim/vim#15519 https://github.com/vim/vim/commit/bc29ea62861052b35781031173a67d7d577be068 Co-authored-by: Christian Brabandt <cb@256bit.org>
| * vim-patch:5f5f283: runtime(pandoc): escape quotes in &errorformat for pandocChristian Clason2024-08-21
| | | | | | | | | | | | | | | | closes: vim/vim#15535 https://github.com/vim/vim/commit/5f5f2832f5dcf845a93f7f62c1daf6cba9c17989 Co-authored-by: Konfekt <Konfekt@users.noreply.github.com>
| * vim-patch:d55e698: runtime(pandoc): refine pandoc compiler settingsChristian Clason2024-08-21
| | | | | | | | | | | | | | | | closes: vim/vim#15529 https://github.com/vim/vim/commit/d55e698fa02195bf451b072eb2fb20cfbf7bddf5 Co-authored-by: Konfekt <Konfekt@users.noreply.github.com>
| * vim-patch:9.1.0686: zip-plugin has problems with special characters (#30108)zeertzjq2024-08-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: zip-plugin has problems with special characters (user202729) Solution: escape '*?[\' on Unix and handle those chars a bit differently on MS-Windows, add a test, check before overwriting files runtime(zip): small fixes for zip plugin This does the following: - verify the unzip plugin is executable when loading the autoload plugin - handle extracting file names with '[*?\' in its name correctly by escaping those characters for the unzip command (and handle those characters a bit differently on MS-Windows, since the quoting is different) - verify, that the extract plugin is not overwriting a file (could cause a hang, because unzip asking for confirmation) - add a test zip file which contains those special file names fixes: vim/vim#15505 closes: vim/vim#15519 https://github.com/vim/vim/commit/7790ea0c680a9f951a86066e5940ec16b2333c9a Co-authored-by: Christian Brabandt <cb@256bit.org>
| * vim-patch:e44e644: runtime(doc): fix grammar in :h :keeppatternszeertzjq2024-08-21
| | | | | | | | | | | | | | | | | | | | - It's clear that :s and :& are Ex commands, so remove "command" along with the duplicate "the". - Use "or" instead of "and" following "without". closes: vim/vim#15527 https://github.com/vim/vim/commit/e44e64492cf0a99191826b05ea5ee80b3a5fb3f5
| * vim-patch:3840d2f: runtime(doc): remove trailing whitespace in cmdline.txtzeertzjq2024-08-21
| | | | | | | | | | | | https://github.com/vim/vim/commit/3840d2feaf1454c934f71a97aae7a56a5ceccef9 Co-authored-by: Christian Brabandt <cb@256bit.org>
| * vim-patch:175a87c: runtime(doc): more clarification for the :keeppatterns neededzeertzjq2024-08-21
| | | | | | | | | | | | https://github.com/vim/vim/commit/175a87c7f163e34876c6848f829970fec61fc9d7 Co-authored-by: Christian Brabandt <cb@256bit.org>
| * fix(lsp): update request name to capability map #30098atusy2024-08-20
| | | | | | | | | | | | | | | | | | | | Add items based on specifications (<https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocumentClientCapabilities>) - textDocument/documentColor - textDocument/inlineValue - textDocument/linkedEditingRange - textDocument/moniker - textDocument/onTypeFormatting - textDocument/selectionRange
| * docs(lsp): annotate with `vim.lsp.protocol.Methods` enum #29521Ricardo Casía2024-08-20
| | | | | | Added the enum type annotation `vim.lsp.protocol.Methods` to provide some intellisense support.
| * fix(vim.text): handle very long strings (#30075)Gregory Anders2024-08-17
| | | | | | | | | | | | | | | | Lua's string.byte has a maximum (undocumented) allowable length, so vim.text.hencode fails on large strings with the error "string slice too long". Instead of converting the string to an array of bytes up front, convert each character to a byte one at a time.
| * vim-patch:8e25d91: runtime(dist): verify that executable is in $PATHChristian Clason2024-08-18
| | | | | | | | | | | | | | | | | | | | | | | | Otherwise, if the executable to be verified does not exist, this would cause a false-positive in the 'IsSafeExecutable()' check, because 'exepath(executable)' returns an empty string and 'fnamemodify('', ':p:h')' returns the current directory and as a result the 'IsSafeExecutable()' returns false (for the wrong reason). https://github.com/vim/vim/commit/8e25d91cb7bb4dc171cb4e95b1bb79a39400a13a Co-authored-by: Christian Brabandt <cb@256bit.org>
| * vim-patch:6908db4: runtime(colors): update colorschemesChristian Clason2024-08-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | - all: PMenuMatch and PMenuMatchSel for 8c/16c - habamax: - revert VertSplit to solid background color - remove gitCommitSummary link to Title - make TabLineFill same as StatuslineNC closes: vim/vim#15506 https://github.com/vim/vim/commit/6908db475603c0f37aaf4c3ba13dfdbebd340003 Co-authored-by: Maxim Kim <habamax@gmail.com>
| * vim-patch:c6ed816: runtime(yaml): do not re-indent when commenting out linesChristian Clason2024-08-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's a personal annoyance for me. I have to edit yaml files on a lot of customer environments and whenever you type '#' at the start of the line, the commented line will be indented by whatever indent the previous line had. I hate this seriously, because it makes un-commenting painful. So let's fix this. But instead of messing with the indent function, let's just remove the '0#' from cinkeys, so that Vim won't perform re-indenting when commenting out such a yaml file. closes: vim/vim#15494 https://github.com/vim/vim/commit/c6ed816761f44da92d8c61f5ea6cb7fdbb45fac5 Co-authored-by: Christian Brabandt <cb@256bit.org>
| * vim-patch:1fbccc1: runtime(netrw): Drop committed trace linesChristian Clason2024-08-17
| | | | | | | | | | | | | | | | closes: vim/vim#15501 https://github.com/vim/vim/commit/1fbccc1e9694e5e6162dff112b49a093eac770ee Co-authored-by: Damien <141588647+xrandomname@users.noreply.github.com>
| * vim-patch:b4d1164: runtime(netrw): Error popup not always usedChristian Clason2024-08-17
| | | | | | | | | | | | | | | | | | | | | | | | Problem: g:netrw_use_errorwindow=2 does not work without +balloon_eval. Solution: Check for popup_atcursor(). related: vim/vim#15501 https://github.com/vim/vim/commit/b4d11644254ec6e29aed93a9fdcde2160163aefd Co-authored-by: Damien <141588647+xrandomname@users.noreply.github.com>
| * vim-patch:7c75411: runtime(netrw): ErrorMsg() may throw E121Christian Clason2024-08-17
| | | | | | | | | | | | | | | | | | | | Move variables declaration related: vim/vim#15501 https://github.com/vim/vim/commit/7c754110ff8e0d666d422f1644bc356c8fee7392 Co-authored-by: Damien <141588647+xrandomname@users.noreply.github.com>
| * vim-patch:a1dc649: runtime(dosbatch): Show %%i as an argument in syntax fileChristian Clason2024-08-17
| | | | | | | | | | | | | | | | | | | | Inside batch files, for-variables must be written as %%i, not %i. closes: vim/vim#15453 https://github.com/vim/vim/commit/a1dc64956f36cb921d556910c5356bb6b91ba5b9 Co-authored-by: Ken Takata <kentkt@csc.jp>
| * vim-patch:11c92be: runtime(dosbatch): Add syn-sync to syntax fileChristian Clason2024-08-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Closing parentheses were often highlighted as errors. Add a syntax sync command to reduce the error. Also fix that `defined` was not highlighted as an operator inside parentheses. E.g.: ``` if defined foo ( if defined bar ( ... ) ) ``` The first `defined` was highlighted but the second one was not. related: vim/vim#15453 https://github.com/vim/vim/commit/11c92be8974f04ab12ff3f9cd89a692bbd6c46d9 Co-authored-by: Ken Takata <kentkt@csc.jp>
| * vim-patch:dd36d6c: runtime(mediawiki): fix typo in doc, test for ↵Christian Clason2024-08-17
| | | | | | | | | | | | | | | | | | | | b:did_ftplugin var closes: vim/vim#15479 https://github.com/vim/vim/commit/dd36d6cc7c39f3cfb29818f89f4f9dec2c7c22e4 Co-authored-by: Stanislav Asunkin <1353637+stasjok@users.noreply.github.com>
| * vim-patch:d164f2a: runtime(vim): Update base-syntax, improve :let-heredoc ↵zeertzjq2024-08-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | highlighting (#30069) The end marker must appear on line of its own without any trailing whitespace. Whitespace is incorrectly allowed before all end markers. Limiting this only to heredocs where "trim" was specified, and with the correct indent, is currently an intractable problem given that contained syntax groups (in this case :let) cannot be limited to start patterns. Highlight interpolated expressions when "eval" is specified. cloess: vim/vim#15511 https://github.com/vim/vim/commit/d164f2a521f8e52e587727657fb1c19e9a25f32a Co-authored-by: Doug Kearns <dougkearns@gmail.com>
| * vim-patch:cba93ca: runtime(doc): clarify the effect of :keeppatterns after ↵zeertzjq2024-08-17
| | | | | | | | | | | | v9.1.0677 https://github.com/vim/vim/commit/cba93cab533b5da26b9e4a4338c1dc6e8aa3d409
| * vim-patch:9.1.0677: :keepp does not retain the substitute patternzeertzjq2024-08-17
| | | | | | | | | | | | | | | | | | | | | | | | | | Problem: :keeppatterns does not retain the substitute pattern for a :s command Solution: preserve the last substitute pattern when used with the :keeppatterns command modifier (Gregory Anders) closes: vim/vim#15497 https://github.com/vim/vim/commit/3b59be4ed8a145d3188934f1a5cd85432bd2433d Co-authored-by: Gregory Anders <greg@gpanders.com>
| * fix(tutor): incorrect lines marked as correct #29833Eduardo Rittner Coelho2024-08-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: In line 308 the poem appears as ✅1) Roses are red, ✅2) Mud is fun, ✅3) Violets are blue, ✅4) I have a car, ✅5) Clocks tell time, ✅6) Sugar is sweet ✅7) And so are you. where the wrong lines (2, 4, 5) are all marked as correct. Solution: Change the tutor.json file so that initially the poem appears as ✅1) Roses are red, ❌2) Mud is fun, ✅3) Violets are blue, ❌4) I have a car, ❌5) Clocks tell time, ❌6) Sugar is sweet ✅7) And so are you. The method for checking whether a line is correct or not is really simple, so I couldn't find a way to display the 6th line as initially correct, however upon deleting lines 2, 4 and 5 the final result shows line 6 as correct.
| * fix(docs): add missing properties to hl_info #30032Maria José Solano2024-08-16
| |
| * fix(man): avoid setting v:errmsg (#30052)zeertzjq2024-08-15
| |
| * feat(term): support OSC 8 hyperlinks in :terminal (#30050)Gregory Anders2024-08-15
| |
| * vim-patch:fc762df: runtime(sql, mysql): fix E169: Command too recursive with ↵Yinzuo Jiang2024-08-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | sql_type_default = "mysql" Problem: When setting "let g:sql_type_default = "mysql", editing .sql file reports "E169: Command too recursive" error Solution: - Add 'let b:did_ftplugin = 1' at the top of ftplugin/sql.vim - Add 'if exists("b:did_ftplugin") | finish | endif' in ftplugin/mysql.vim - Add missing header information in ftplugin/mysql.vim - Remove redundant code in ftplugin/sql.vim fixes: vim/vim#15474 closes: vim/vim#15475 https://github.com/vim/vim/commit/fc762dfc9fa95696409067bcb565e846c9ccfc5a Signed-off-by: Yinzuo Jiang <jiangyinzuo@foxmail.com> Signed-off-by: Riley Bruins <ribru17@hotmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
| * vim-patch:ea76096: runtime(javascript): fix a few issues with syntax ↵tobil4sk2024-08-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | higlighting (#30049) It addresses the following issues: - Fix highlight of let and var javascript keywords According to runtime/doc/syntax.txt, Identifier is for variable names. let/var are not variable names, they are keywords - Add highlighting for "from" keyword in javascript - Fix highlight of function keyword in javascript According to docs, Function is for function names, so the function keyword should just be Keyword. - Fix highlight of static keyword in javascript According to vim docs: StorageClass static, register, volatile, etc. closes: vim/vim#15480 https://github.com/vim/vim/commit/ea76096fa98ac26c23703bffdc4d9b3dc8a94d7e
| * vim-patch:dc831db: runtime(doc): add help tags for json + markdown global ↵zeertzjq2024-08-13
| | | | | | | | | | | | | | | | | | | | | | | | variables (#30037) I added help tags for them in the syntax.txt file since this is the only place they are mentioned. closes: vim/vim#15486 https://github.com/vim/vim/commit/dc831db6ea3b550e3acb60a0859fcd07fd3f86e6 Co-authored-by: JJCUBER <34446698+JJCUBER@users.noreply.github.com>
| * fix(loader): follow the style of the error message for built-in loadersfutsuuu2024-08-13
| | | | | | | | | | start the error message with '\n\t' instead of '\n' surround the module name by single quotes
| * fix(lua): ignore stdout and stderr for xdg-openAaron2024-08-12
| | | | | | | | Ref #19724 Fix #29932
| * test(lsp): refactor and tidyLewis Russell2024-08-11
| | | | | | | | | | | | | | - Merge all the top level 'LSP' describe blocks - Refactor text edit tests - Fix typing errors - Add linebreaks between tests
| * feat(term): enable reflow by default (#21124)Christian Clason2024-08-10
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Contents of terminal buffer are not reflown when Nvim is resized. Solution: Enable reflow in libvterm by default. Now that libvterm is vendored, also fix "TUI rapid resize" test failures there. Note: Neovim's scrollback buffer does not support reflow (yet), so lines vanishing into the buffer due to a too small window will be restored without reflow.
| * build(deps): vendor libvterm at v0.3.3Christian Clason2024-08-10
| | | | | | | | | | | | | | | | Problem: Adding support for modern Nvim features (reflow, OSC 8, full utf8/emoji support) requires coupling libvterm to Nvim internals (e.g., utf8proc). Solution: Vendor libvterm at v0.3.3.
| * vim-patch:0cc5dce: runtime(doc): clarify directory of Vim's executable vs CWDzeertzjq2024-08-09
| | | | | | | | | | | | | | | | | | | | According to :h win32-PATH, "the same directory as Vim" means the same directory as the Vim executable, not Vim's current directory. In patch 8.2.4860 these two concepts were mixed up. closes: vim/vim#15451 https://github.com/vim/vim/commit/0cc5dce5780d39fe621f6146d4fb862318918125
| * vim-patch:39eff4c: runtime(proto): Add indent script for protobuf filetypeChristian Clason2024-08-08
| | | | | | | | | | | | | | | | closes: vim/vim#15446 https://github.com/vim/vim/commit/39eff4cdc055a0f0db0d32fcf7a74fe30ea54f25 Co-authored-by: David Pedersen <limero@me.com>
| * fix(lsp): avoid reusing diagnostics from different servers in actions (#30002)Grzegorz Rozdzialik2024-08-07
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: When preparing the parameters for a code actions LSP request, the code set `context.diagnostics` when processing the first LSP client, and then reused those `context.diagnostics` for subsequent LSP clients. This meant that the second and next LSP clients got diagnostics that did not originate from them, and they did not get the diagnostics that they sent. Solution: Avoid setting `context.diagnostics` (which is referenced by all clients). Instead, set `params.context.diagnostics` directly, which is specific to a single client. Fixes #30001 Caused by #29501
| * vim-patch:afea6b9: runtime(zip): use defer to restore old settingszeertzjq2024-08-07
| | | | | | | | | | | | | | | | | | | | Problem: RestoreOpts() plugin called too often Solution: use :defer to have the RestoreOpts() function called when the function returns automatically https://github.com/vim/vim/commit/afea6b946827e964271eb19579946a7f88d2f329 Co-authored-by: Christian Brabandt <cb@256bit.org>
| * vim-patch:8d52926: runtime(zip): add a generic Message functionzeertzjq2024-08-07
| | | | | | | | | | | | | | | | | | | | Problem: the zip plugin duplicates a lot of code for displaying warnings/errors Solution: refactor common code into a generic Mess() function https://github.com/vim/vim/commit/8d52926857ec7f08a9bee8f96470748cecf58002 Co-authored-by: Christian Brabandt <cb@256bit.org>
| * vim-patch:a336d8f: runtime(zip): increment base version of zip pluginzeertzjq2024-08-07
| | | | | | | | | | | | | | | | | | Problem: the zip plugin version is still v33 Solution: increment the version to v34 https://github.com/vim/vim/commit/a336d8f21e4cce877e23d47db238801a5a406992 Co-authored-by: Christian Brabandt <cb@256bit.org>
| * vim-patch:19636be: runtime(zip): refactor save and restore of optionszeertzjq2024-08-07
| | | | | | | | | | | | | | | | | | | | | | | | | | Problem: zip plugin has no way to set/restore option values Solution: Add the SetSaneOpts() and RestoreOpts() functions, so options that cause issues are set to sane values and restored back to their initial values later on. (this affects the 'shellslash' option on windows, which also changes how the shellescape() function works) https://github.com/vim/vim/commit/19636be55e023cb726389107e9e7d62049b6fd58 Co-authored-by: Christian Brabandt <cb@256bit.org>
| * vim-patch:33836d3: runtime(zip): remove test for fnameescapezeertzjq2024-08-07
| | | | | | | | | | | | | | | | | | | | Problem: zip plugin tests for fnameescape() function Solution: Remove the check, fnameescape() has been available since 7.1.299, it should nowadays always be available https://github.com/vim/vim/commit/33836d38b82aa926a2a2b3f945a0139f373f7e56 Co-authored-by: Christian Brabandt <cb@256bit.org>
| * vim-patch:120c0dd: runtime(zip): use :echomsg instead of :echozeertzjq2024-08-07
| | | | | | | | | | | | | | | | | | | | Problem: zip plugin uses :echo which does not store messages Solution: use :echomsg instead of :echo so that messages are stored in the message history https://github.com/vim/vim/commit/120c0dd815fa3b44df0fa477f7f3313e4a69c652 Co-authored-by: Christian Brabandt <cb@256bit.org>
| * vim-patch:a63f66e: runtime(zip): clean up and remove commentszeertzjq2024-08-07
| | | | | | | | | | | | | | | | | | Problem: zip plugin contains a lot of comments from the decho plugin Solution: Clean up and remove un-used comments https://github.com/vim/vim/commit/a63f66e953d811bb6d044e92fe338e533ad94ff5 Co-authored-by: Christian Brabandt <cb@256bit.org>
| * docs(treesitter): generate inline docs for `Range`sYi Ming2024-08-06
| | | | | | | | | | | | | | | | docs(treesitter): in-place parameter description docs(treesitter): remove internal type names docs(treesitter): add missing private annotation
| * vim-patch:8.2.4838: checking for absolute path is not trivial (#29990)zeertzjq2024-08-06
| | | | | | | | | | | | | | | | | | | | Problem: Checking for absolute path is not trivial. Solution: Add isabsolutepath(). (closes vim/vim#10303) https://github.com/vim/vim/commit/dca1d40cd0f2af0755519e7028378bd3c8fefd31 vim-patch:8a3b805c6c9c Co-authored-by: LemonBoy <thatlemon@gmail.com>
| * vim-patch:9.1.0465: missing filecopy() function (#29989)zeertzjq2024-08-06
| | | | | | | | | | | | | | | | | | | | | | Problem: missing filecopy() function Solution: implement filecopy() Vim script function (Shougo Matsushita) closes: vim/vim#12346 https://github.com/vim/vim/commit/60c8743ab6c90e402e6ed49d27455ef7e5698abe Co-authored-by: Shougo Matsushita <Shougo.Matsu@gmail.com>
| * vim-patch:f0e9b72: runtime(zip): Fix for FreeBSD's unzip commandzeertzjq2024-08-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Cannot browse zipfiles with the unzip program found on FreeBSD. Solution: Adjust command arguments. Unzip found on FreeBSD complain about missing argument with the zipinfo modifier '-Z -1'. Joining arguments seems to work for both implementations. Also change `:sil!` to `:sil` so that error messages are properly reported (per review of Christian Brabandt). related: vim/vim#15411 https://github.com/vim/vim/commit/f0e9b72c8fdd47b9b410a11edf7479953cb2aed9 Co-authored-by: Damien <141588647+xrandomname@users.noreply.github.com>