aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
| * | | build(deps): tree-sitter-vimdoc v2.0.1Justin M. Keyes2023-06-26
| | | |
* | | | fix(startup): "nvim -l foo.lua" may not set arg0 #24161Mike2023-06-26
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Using "nvim -l args.lua" without passing extra script args, does not set `_G.arg[0]`. Steps to reproduce: ``` cat > args.lua<<EOF vim.print(_G.arg, '') vim.print(vim.v.argv, '') EOF nvim --clean -l args.lua ``` Solution: Fix condition in command_line_scan.
* | | docs: fix misparsed headings (#24162)Christian Clason2023-06-26
| | | | | | | | | | | | | | | | | | Problem: vimdoc parser requires space between column heading and `~`. Solution: Add space to docs (and mention it). Also edit `luaref.txt` headings for consistency.
* | | fix(treesitter): update lua parser and queries (#24148)Christian Clason2023-06-26
| | |
* | | fix(charset): fix wrong display of 0xffff (#24158)zeertzjq2023-06-26
| | |
* | | Merge pull request #24154 from zeertzjq/vim-9.0.1665zeertzjq2023-06-26
|\ \ \ | | | | | | | | vim-patch:8.2.3833,9.0.1665
| * | | vim-patch:9.0.1665: empty CmdlineEnter autocommand causes errors in Ex modezeertzjq2023-06-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Empty CmdlineEnter autocommand causes errors in Ex mode. Solution: Save and restore ex_pressedreturn. (Christian Brabandt, closes # 12581, closes vim/vim#12578) https://github.com/vim/vim/commit/590aae35575cbd74d80c41d87fc647f2812aad70 Co-authored-by: Christian Brabandt <cb@256bit.org>
| * | | vim-patch:8.2.3833: error from term_start() not caught by try/catchzeertzjq2023-06-26
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Error from term_start() not caught by try/catch. Solution: save and restore did_emsg when applying autocommands. (Ozaki Kiichi, closes vim/vim#9361) https://github.com/vim/vim/commit/c3f91c0648f4b04a6a9ceb4ccec45ea767a63796 Co-authored-by: ichizok <gclient.gaap@gmail.com>
* | | fix(docs): too much whitespace around <pre> blocks #24151Justin M. Keyes2023-06-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: In the generated docs HTML there is too much whitespace before/after `<pre>` blocks. - In the old layout (fixed-width), all text in `.old-help-para` is formatted as `white-space:pre`. - In the new layout, when `<pre>` is at the end of a `<div>`, the margins of both are redundant, causing too much space. Solution: - In the old layout, always remove `<pre>` margin. - In the new layout, disable `<pre>` margin if it is the last child.
* | | Merge #24116 from justinmk/docJustin M. Keyes2023-06-25
|\ \ \
| * | | docs: autocmds, miscJustin M. Keyes2023-06-25
| | | |
| * | | fix(docs): vimdoc syntax errorsJustin M. Keyes2023-06-25
| | | | | | | | | | | | | | | | gen_help_html: truncate parse-error sample text
* | | | vim-patch:9.0.1663: Termdebug on MS-Windows: some file names are not ↵zeertzjq2023-06-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | recognized (#24145) Problem: Termdebug on MS-Windows: some file names are not recognized. Solution: Do not always change \t and \n. (Christian Brabandt, closes vim/vim#12565, closes vim/vim#12560, closes vim/vim#12550) https://github.com/vim/vim/commit/c9a4a8ab28da2b11856a3f08ccba2e91f46b85c3 Co-authored-by: Christian Brabandt <cb@256bit.org>
* | | | vim-patch:9.0.1661: BUCK files are not recognized (#24142)Christian Clason2023-06-24
| |/ / |/| | | | | | | | | | | | | | | | | | | | Problem: BUCK files are not recognized. Solution: Recognize BUCK files as "bzl". (Son Luong Ngoc, closes vim/vim#12564) https://github.com/vim/vim/commit/b46e0f3263acd99c61df06ee3c4d1f6e0b471bc3 Co-authored-by: Son Luong Ngoc <sluongng@gmail.com>
* | | test(extmarks): add a test for #23848 (#24140)zeertzjq2023-06-24
| | |
* | | vim-patch:9.0.1659: Termdebug: default highlight cleared if changing ↵zeertzjq2023-06-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | colorscheme (#24139) Problem: Termdebug: default highlight cleared when changing colorscheme. Solution: Use a ColorScheme autocommand. (Christian Brabandt, closes vim/vim#12566, closes vim/vim#12555) https://github.com/vim/vim/commit/279de0cd1f58ea520826a3dd1c5562a71157b23b Co-authored-by: Christian Brabandt <cb@256bit.org>
* | | Merge pull request #24082 from smjonas/fix_24064Christian Clason2023-06-24
|\ \ \ | | | | | | | | fix(filetype): correctly detect bash-fc-{id} files as "sh" (vim-patch:9.0.1644)
| * | | fix(filetype): correctly detect bash-fc-{id} files as "sh"smjonas2023-06-23
| | | |
| * | | vim-patch:9.0.1644: not all filetype file name matches are testedsmjonas2023-06-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Not all filetype file name matches are tested. Solution: Add more file names to test with. (Jonas Strittmatter, closes vim/vim#12569) https://github.com/vim/vim/commit/bd087ae8f07f026bbd179911830027ff92f42c01 Co-authored-by: smjonas <jonas.strittmatter@gmx.de>
* | | | fix(extmarks): fix heap buffer overflow caused by inline virtual text (#23851)Ibby2023-06-24
| | | | | | | | | | | | also fixes an edge case where the extends character would not be drawn if the real text exactly fits the grid.
* | | | fix(lsp): error in reset_timer on second detach #24117Chinmay Dalal2023-06-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: On running `zig fmt` manually, the on_lines callback and the server both detach (for some reason), and both of them call `clear()`. This fixes it, otherwise the second one to detach has an error in `reset_timer` since the bufstate doesn't exist Solution: * exit early in clear if `bufstates[bufnr]` is nil * set bufstatte.enabled to true on reload instead of making bufstate nil
* | | | ci: introduce CI_LINT optiondundargoc2023-06-24
| | | | | | | | | | | | | | | | | | | | | | | | This will abort if lint programs are not found, and is meant primarily for the lint job in CI. Supersedes the REQUIRED argument in add_glob_target as it's a superior replacement by being a built-in solution.
* | | | build(luarc.json): disable luadoc-miss-see-name #24108Raphael2023-06-23
| | | |
* | | | fix(lsp): reapplying already-applied hints #24114Chinmay Dalal2023-06-23
| |/ / |/| | | | | | | | | | | | | | | | | | | | | | | Problem: The decoration provider clears the whole buffer then redraws all the hints every time the window was redrawn. This may lead to an infinite loop. Solution: Store the last applied version for a line and only clear and redraw the line if the buffer version has changed.
* | | fix(cmdline): don't redraw 'tabline' in Ex mode (#24123)zeertzjq2023-06-23
| | | | | | | | | | | | | | | | | | | | | | | | Redrawing of 'statusline' and 'winbar' are actually already inhibited by RedawingDisabled in Ex mode. In Vim there is a check for `msg_scrolled == 0` (which is false in Ex mode) since Vim doesn't have msgsep. Add a `!exmode_active` check here in Nvim instead.
* | | feat(lsp): opt-in to dynamicRegistration for inlay hints (#24102)Mathias Fußenegger2023-06-22
| | | | | | | | | | | | | | | Since https://github.com/neovim/neovim/pull/23681 there is dynamic registration support. We should use that for new features unless there is a good reason to turn it off.
* | | vim-patch:9.0.1645: zserio files are not recognized (#24120)Christian Clason2023-06-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: zserio files are not recognized. Solution: Add a pattern for zserio files. (Dominique Pellé, closes vim/vim#12544) https://github.com/vim/vim/commit/2b994da57a0ac6ec0ec09fe3783f48ecd2bce610 Co-authored-by: =?UTF-8?q?Dominique=20Pell=C3=A9?= <dominique.pelle@gmail.com>
* | | feat(extmarks): support hl_mode "combine" for inline virt_text (#24099)zeertzjq2023-06-22
| | |
* | | feat(lsp): soft deprecate vim.lsp.for_each_buffer_client (#24104)Mathias Fußenegger2023-06-22
| | | | | | | | | | | | | | | | | | | | | There is no need for two ways to access all clients of a buffer. This doesn't add a `vim.deprecate` call yet, as the function is probably used a lot, but removes it from the documentation and annotates it with `@deprecated`
* | | fix(messages): use "Vimscript" instead of "VimL" #24111Justin M. Keyes2023-06-22
| | | | | | | | | | | | followup to #24109 fix #16150
* | | test: spellcheck :help (vimdoc) files #24109Justin M. Keyes2023-06-22
| | | | | | | | | | | | | | | | | | | | | Enforce consistent terminology (defined in `gen_help_html.lua:spell_dict`) for common misspellings. This does not spellcheck English in general (perhaps a future TODO, though it may be noisy).
* | | fix(extmarks): hide inline virt_text properly with 'smoothscroll' (#24106)zeertzjq2023-06-22
| | |
* | | fix(extmarks): empty inline virt_text interfering with DiffText (#24101)zeertzjq2023-06-22
| | |
* | | Merge #24087 from justinmk/docJustin M. Keyes2023-06-22
|\ \ \ | | | | | | | | docs: lsp, fix errors, gen_help_html features
| * | | feat(gen_help_html): ignore pi_netrw.txt errorsJustin M. Keyes2023-06-22
| | | | | | | | | | | | | | | | IDGAF about netrw
| * | | feat(gen_help_html): non-default vimdoc.so parserJustin M. Keyes2023-06-22
| | | | | | | | | | | | | | | | Callers can specify a non-default vimdoc.so file path.
| * | | fix(docs): vimdoc syntax errorsJustin M. Keyes2023-06-22
| | | | | | | | | | | | | | | | | | | | | | | | Since https://github.com/neovim/tree-sitter-vimdoc/pull/97 the many cases of *.foo cause parser errors. But even before that, these were erroneously highlighted as (argument), so fixing them is good.
| * | | docs: lsp, vim_diffJustin M. Keyes2023-06-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | - quickstart - mark lsp.txt as `new_layout` - remove lsp-handler documentation for notifications: they don't have handlers because they don't have server responses.
* | | | perf(lsp): remove grouping logic from lsp.status (#24096)Mathias Fußenegger2023-06-22
|/ / / | | | | | | | | | With the title carry-over logic in the `$/progress` handler it's not necessary to group again in vim.lsp.status
* | | Merge pull request #24098 from zeertzjq/fix-extmarkzeertzjq2023-06-22
|\ \ \ | | | | | | | | Fix two extmark bugs
| * | | fix(api): wrong nvim_buf_set_extmark error for invalid hl_modezeertzjq2023-06-22
| | | |
| * | | fix(extmarks): empty inline virt_text interfering with Visual highlightzeertzjq2023-06-22
| | | |
* | | | fix: tostring(vim.version()) fails if build is NIL #24097Julian Grinblat2023-06-22
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Since #23925, Version.build may be vim.NIL, which causes tostring() to fail: E5108: Error executing lua E5114: Error while converting print argument #1: …/version.lua:129: attempt to concatenate field 'build' (a userdata value) stack traceback: [C]: in function 'print' [string ":lua"]:1: in main chunk Solution: Handle vim.NIL in Version:__tostring().
* | | feat(man): respect 'wrapmargin' when wrapping man pages (#24091)Gregory Anders2023-06-21
| | |
* | | Merge #24086 LSP ctx.version, report full Nvim versionJustin M. Keyes2023-06-21
|\ \ \
| * | | docs(lsp): mention ctx.versionJustin M. Keyes2023-06-21
| | | | | | | | | | | | | | | | | | | | Since 643546b82b4bc0c29ca869f81af868a019723d83 the request handler context (`ctx`) includes a `version` field.
| * | | refactor(lsp): report full Nvim version string in clientInfoJustin M. Keyes2023-06-21
| | | |
* | | | fix(folds): don't show search or match highlighting on fold (#24084)zeertzjq2023-06-21
|/ / /
* | | fix(vim.json)!: remove global options, "null", "array_mt" #24070Justin M. Keyes2023-06-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: - `vim.json` exposes various global options which: - affect all Nvim Lua plugins (especially the LSP client) - are undocumented and untested - can cause confusing problems such as: https://github.com/codota/tabnine-nvim/commit/cc76ae3abe2f129d44b5a8edee2529e0ee0dcf69 - `vim.json` exposes redundant mechanisms: - `vim.json.null` is redundant with `vim.NIL`. - `array_mt` is redundant because Nvim uses a metatable (`vim.empty_dict()`) for empty dict instead, which `vim.json` is configured to use by default (see `as_empty_dict`). Example: ``` :lua vim.print(vim.json.decode('{"bar":[],"foo":{}}')) --> { bar = {}, foo = vim.empty_dict() } ``` Thus we don't need to also decorate empty arrays with `array_mt`. Solution: Remove the functions from the public vim.json interface. Comment-out the implementation code to minimize drift from upstream. TODO: - Expose the options as arguments to `vim.json.new()`
* | | fix(lsp): add spacing for inlay hints separately #24079Akin2023-06-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Spacing around inlay hints has the same highlight as the hint itself. The LSP spec for inlay hints specifically mentions the padding should not be coloured: /** Render padding before the hint. Note: Padding should use the editor's background color, not the background color of the hint itself. That means padding can be used to visually align/separate an inlay hint. */ paddingLeft?: boolean; /** Render padding after the hint. Note: Padding should use the editor's background color, not the background color of the hint itself. That means padding can be used to visually align/separate an inlay hint. */ paddingRight?: boolean; Solution: Add the space as separate parts of the virtual text, don't add the space to the text itself.
generated by cgit (git 2.34.1) at 2025-07-12 13:01:27 +0000