aboutsummaryrefslogtreecommitdiff
path: root/runtime
Commit message (Collapse)AuthorAge
...
| * docs(options): add codeblock annotations to options.lua (#26696)Christian Clason2023-12-22
| | | | | | | | | | Also consistently remove leading colons in examples Co-authored-by: zeertzjq <zeertzjq@outlook.com>
| * vim-patch:9.0.2183: Maximum callback depth is not configurable (#26703)zeertzjq2023-12-22
| | | | | | | | | | | | | | | | | | Problem: Maximum callback depth is not configurable. Solution: Revert patch 9.0.2103. Set 'maxfuncdepth' in test. fixes: vim/vim#13732 closes: vim/vim#13736 https://github.com/vim/vim/commit/fe583b1e5987fbfdb5f2141c133dbff9665ed301
| * vim-patch:0630080bbd3e (#26704)zeertzjq2023-12-22
| | | | | | | | | | | | | | runtime(doc): reformat and align :h ft-c-syntax (vim/vim#13738) https://github.com/vim/vim/commit/0630080bbd3ece71737daf657d51f6a4ebc19906 Co-authored-by: Christian Brabandt <cb@256bit.org>
| * vim-patch:18ab6c3392efChristian Clason2023-12-22
| | | | | | | | | | | | | | | | | | | | | | | | | | runtime(erlang): add support for matchit plugin (vim/vim#13713) This commit updates the Erlang runtime files to be in sync with the `vim-erlang-runtime` repository. In particular, it adds the following commit (with some cleanup and simplification afterwards): https://github.com/vim-erlang/vim-erlang-runtime/commit/6ea8b85bc9c93b94c68ec53489a74f5687d898b0 https://github.com/vim/vim/commit/18ab6c3392ef83abf078042e233d085fe80b6c06 Co-authored-by: Csaba Hoch <csaba.hoch@gmail.com>
| * vim-patch:37468879977aChristian Clason2023-12-22
| | | | | | | | | | | | | | | | | | | | runtime(masm): add variants of opcodes (vim/vim#13734) that can actually be generated by compilers https://github.com/vim/vim/commit/37468879977ae32ab49f8fb15c4c458eb3efcdb8 Co-authored-by: Wu Yongwei <wuyongwei@gmail.com>
| * vim-patch:21064ebcd609Christian Clason2023-12-22
| | | | | | | | | | | | | | | | | | | | | | | | | | runtime(vim): Update syntax file (vim/vim#13739) Match all ex commands after ":" and the "|" command separator. Exceptions are not handled yet and :insert/:change/:append are still not matched after the command separator bar. https://github.com/vim/vim/commit/21064ebcd609b1dfcf63c55dca32e6465102d461 Co-authored-by: dkearns <dougkearns@gmail.com>
| * vim-patch:cc944b145254Christian Clason2023-12-22
| | | | | | | | | | | | | | | | runtime(json5): Add TODO support to syntax script (vim/vim#13743) https://github.com/vim/vim/commit/cc944b1452547145cdd947a37c75fce695d8571e Co-authored-by: Danek Duvall <duvall@comfychair.org>
| * feat: generate types and docs for v variablesLewis Russell2023-12-21
| |
| * docs: move vim-variables to separate fileLewis Russell2023-12-21
| |
| * fix(runtime): source old color scheme in bundled color schemes (#26641)Evgeni Chasnovski2023-12-21
| | | | | | | | | | | | | | | | | | | | | | Problem: Bundled color schemes use `:hi clear` and only define Vim's highlight groups. This results into Nvim-specific highlight groups using definitions from Nvim's default color scheme, which are not always linked to a Vim's highlight group. Solution: Restore links to Vim's highlight groups which were present before Nvim's default color scheme update.
| * refactor(runtime): rewrite 'vim' color scheme in LuaEvgeni Chasnovski2023-12-21
| | | | | | | | | | | | | | | | | | | | Problem: Bundled 'vim' color scheme is written in Vimscript which implicitly assumes that the file is ported from Vim. This is not the case, at it is currently the Neovim's way of providing backward compatibility for color schemes. Solution: Rewrite it in Lua to indicate that this runtime file comes from Neovim.
| * fix(osc52): use nvim_chan_send() to stderr for copying (#26690)zeertzjq2023-12-21
| | | | | | | | | | | | | | The data to be written can be very long, so use nvim_chan_send() instead of io.stdout:write() as the latter doesn't handle EAGAIN. A difference of these two approaches is that nvim_chan_send() writes to stderr, not stdout, so it won't work if client stderr is redirected.
| * docs: apply current colorscheme to default highlight groupsChristian Clason2023-12-20
| | | | | | | | | | | | Problem: Not all default highlight groups show their actual colors. Solution: Refactor `vimhelp.lua` and apply it to all relevant lists (UI groups, syntax groups, treesitter groups, LSP groups, diagnostic groups).
| * docs: remove section on constants in style guidedundargoc2023-12-20
| | | | | | | | It is needlessly restrictive and specific without good reason.
| * refactor(treesitter): cleanup highlighterLewis Russell2023-12-20
| | | | | | | | | | | | | | | | - Remove some unused fields - Prefix classes with `vim.` - Move around some functions so the query stuff is at the top. - Improve type hints - Rework how hl_cache is implemented
| * docs: document header structuredundargoc2023-12-20
| | | | | | | | Reference: https://github.com/neovim/neovim/issues/6371
| * vim-patch:955652f6df9c (#26667)zeertzjq2023-12-20
| | | | | | | | | | | | | | | | | | runtime(doc): Update change.txt (vim/vim#13725) Fix-up and clarify commit e06f2b498ccca921f34a1bec4464f042a5a2cabd https://github.com/vim/vim/commit/955652f6df9c4a1048fde8028c5c7f7871b5f71a Co-authored-by: K.Takata <kentkt@csc.jp>
| * vim-patch:9.0.2179: no filetype detection for execline scriptsChristian Clason2023-12-19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: no filetype detection for execline scripts Solution: Add filetype detection for execline as a prior to adding syntax support for execline (see https://github.com/djpohly/vim-execline/issues/2), i went ahead and made the filetype detection for execline scripts. closes: vim/vim#13689 Signed-Off-By: Mazunki Hoksaas <rolferen@gmail.com> https://github.com/vim/vim/commit/63210c214afa6589b6132bd060908a8711f4567f Co-authored-by: Mazunki Hoksaas <rolferen@gmail.com>
| * vim-patch:fbd72d2d4725Christian Clason2023-12-19
| | | | | | | | | | | | | | | | runtime(netrw): prevent E11 on FocusGained autocommand (vim/vim#13718) https://github.com/vim/vim/commit/fbd72d2d47257267bc6e3fe093ef8c225369ab79 Co-authored-by: Christian Brabandt <cb@256bit.org>
| * vim-patch:379df7c1dbb2Christian Clason2023-12-19
| | | | | | | | | | | | | | | | | | | | | | runtime(8th): updated 8th syntax (vim/vim#13720) * updated 8th.vim * removed obsolete code https://github.com/vim/vim/commit/379df7c1dbb23d44918c7fbf102c4a0f7bdc2132 Co-authored-by: ronaaron <ron@aaron-tech.com>
| * fix(treesitter): prepare highlight states for [s, ]sJaehwang Jung2023-12-19
| |
| * docs: small fixes (#26448)dundargoc2023-12-19
| | | | | | | | Co-authored-by: Gregory Anders <8965202+gpanders@users.noreply.github.com> Co-authored-by: Jordan Mandel <jordan.mandel@live.com>
| * feat(api): add forward and back mouse buttonsAmanda Graven2023-12-18
| |
| * refactor: soft-deprecate diagnostic signs configured with :sign-define (#26618)Gregory Anders2023-12-18
| | | | | | | | | | Diagnostic signs should now be configured with vim.diagnostic.config(), but "legacy" sign definitions should go through the standard deprecation process to minimize the impact from breaking changes.
| * feat(termdebug): improve `:Evaluate` floating window (#26621)Jaehwang Jung2023-12-18
| | | | | | | | | | | | | | | | | | | | | | Problem: - The :Evaluate result window is not cleaned up when the cursor moves. - This window is not focusable. Solution: Replace the old implementation from autozimu/LanguageClient-neovim with vim.lsp.util.open_floating_preview and implement custom focusing logic. Also remove g:termdebug_useFloatingHover option now that it's working correctly.
| * docs: add style rule regarding initializationdundargoc2023-12-18
| | | | | | | | | | Specifically, specify that each initialization should be done on a separate line.
| * vim-patch:b42703a662e8Christian Clason2023-12-18
| | | | | | | | | | | | | | | | runtime(tmux): Update tmux syntax rules (vim/vim#13708) https://github.com/vim/vim/commit/b42703a662e87ef0ab643f417869851f065eaac4 Co-authored-by: Eric Pruitt <eric.pruitt@gmail.com>
| * vim-patch:71cbe8e17a8cChristian Clason2023-12-18
| | | | | | | | | | | | | | | | | | | | | | | | | | runtime(fortan): update fortran syntax rules and doc notes Update to the Fortran 2023 standard. Reorganize some code to reflect the dropping of dialect support in the previous commit. Minor improvements. closes: vim/vim#13712 https://github.com/vim/vim/commit/71cbe8e17a8c0c29b91943a7e9da596d718c79cf Co-authored-by: Ajit-Thakkar <142174202+Ajit-Thakkar@users.noreply.github.com>
| * docs(diagnostic): add return value of `vim.diagnostic.config()` (#26615)Yi Ming2023-12-17
| |
| * perf(treesitter): filter out trees outside the visible range earlyJaehwang Jung2023-12-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Treesitter highlighter's on_line was iterating all the parsed trees, which can be quite a lot when injection is used. This may slow down scrolling and cursor movement in big files with many comment injections (e.g., lsp/_meta/protocol.lua). Solution: In on_win, collect trees inside the visible range, and use them in on_line. NOTE: This optimization depends on the correctness of on_win's botline_guess parameter (i.e., it's always greater than or equal to the line numbers passed to on_line). The documentation does not guarantee this, but I have never noticed a problem so far.
| * refactor(lsp): move changetracking to separate file (#26577)Lewis Russell2023-12-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * refactor(lsp): move changetracking to separate file - Prefixed changetracking types with `vim.lsp.` * fixup!: make _reset_timer a local function * fixup!: remove @private annotations * fixup!: changetracking.lua -> _changetracking.lua * fixup! types * fixup! add send_changes_for_group
| * build: cmake fixesdundargoc2023-12-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | - add EXTERNALPROJECT_OPTIONS variable to main build - use `REQUIRED` keyword for IWYU. - remove check_c_compiler_flag checks when `ENABLE_COMPILER_SUGGESTIONS` is `ON`. If we explicitly enable it then we probably want it to give an error if it doesn't exist, rather than silently skip it. - Move dependency interface libraries to their find module and use them as a pseudo-imported target. - Remove BUSTED_OUTPUT_TYPE. It's not used and we can reintroduce it again if something similar is needed. - Use LINK_OPTIONS intead of LINK_FLAGS when generating the `--version` output.
| * refactor: only reload colorscheme if &bg changed (#26598)Gregory Anders2023-12-16
| | | | | | | | | | | | | | | | | | | | Currently, setting &bg at all re-initializes highlights and reloads the active colorscheme, even if the actual value of &bg has not changed. With https://github.com/neovim/neovim/pull/26595 this causes a regression since &bg is set unconditionally based on the value detected from the terminal. Instead, only reload the colorscheme if the actual value of &bg has changed.
| * build: bump minimum cmake version to 3.13dundargoc2023-12-16
| | | | | | | | | | | | | | | | | | | | | | The benefits are primarily being able to use FetchContent, which allows for a more flexible dependency handling. Other various quality-of-life features such as `-B` and `-S` flags are also included. This also removes broken `--version` generation as it does not work for version 3.10 and 3.11 due to the `JOIN` generator expression. Reference: https://github.com/neovim/neovim/issues/24004
| * vim-patch:82f19734bfcbChristian Clason2023-12-16
| | | | | | | | | | | | | | | | | | | | | | runtime(doc): remove deprecation warning for gdefault Deprecated can be misunderstood as being slated for removal; slightly change wording to be clearer. https://github.com/vim/vim/commit/82f19734bfcbddbaee8d5d837f7b7a7119366020 Co-authored-by: dundargoc <gocdundar@gmail.com>
| * vim-patch:0f61943eb776Christian Clason2023-12-16
| | | | | | | | | | | | | | | | runtime(logtalk): Update Logtalk runtime files for the latest language spec (vim/vim#13697) https://github.com/vim/vim/commit/0f61943eb7769777a281e0f8b8ba4c5f46d13e84 Co-authored-by: Paulo Moura <pmoura@logtalk.org>
| * vim-patch:5eb9cb53d619Christian Clason2023-12-16
| | | | | | | | | | | | | | | | | | | | | | | | | | runtime(racket): update Racket runtime files (vim/vim#13693) This brings the included Racket runtime files to commit 43bfc87 (update headers, 2023-12-15) of https://github.com/benknoble/vim-racket. Note that not all files from that repository are included. (In particular, the ftdetect script is omitted for now.) https://github.com/vim/vim/commit/5eb9cb53d619f89251d22299e2cb4f21918d9d38 Co-authored-by: D. Ben Knoble <ben.knoble+github@gmail.com>
| * vim-patch:0378f07fbaeeChristian Clason2023-12-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | runtime(colorschemes): Update colorschemes (vim/vim#13691) Minor changes: - Regenerated using colortemplate 2.2.3 - Removed reversed gui-cursor for some of the colorschemes (retrobox, wildcharm, lunaperche) - Change MatchParen for some of colorschemes. https://github.com/vim/vim/commit/0378f07fbaee9fd8773f3cf8cef146606dd7bf72 Co-authored-by: Maxim Kim <habamax@gmail.com>
| * feat(highlight): tweak default color schemeEvgeni Chasnovski2023-12-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Updating default color scheme produced some feedback. Solution: Address the feedback. Outline of the changes: - Colors `Grey1` and `Grey2` are made a little bit more extreme (dark - darker, light - lighter) to increase overall contrast. - `gui` colors are treated as base with `cterm` colors falling back to using 0-15 colors which come from terminal emulator. - Update highlight group definition to not include attribute definition if it is intended to staty uncolored. - Tweak some specific highlight groups. - Add a list of Neovim specific highlight groups which are now defined differently in a breaking way. - Minor tweaks in several other places related to default color scheme.
| * feat(ui): completeopt support popup like vimmathew2023-12-16
| |
| * Merge pull request #26512 from famiu/refactor/options/type_flagsbfredl2023-12-16
| |\ | | | | | | refactor(options): remove option type macros
| | * refactor(options): remove option type macrosFamiu Haque2023-12-14
| | | | | | | | | | | | | | | | | | | | | | | | Problem: We have `P_(BOOL|NUM|STRING)` macros to represent an option's type, which is redundant because `OptValType` can already do that. The current implementation of option type flags is also too limited to allow adding multitype options in the future. Solution: Remove `P_(BOOL|NUM|STRING)` and replace it with a new `type_flags` attribute in `vimoption_T`. Also do some groundwork for adding multitype options in the future. Side-effects: Attempting to set an invalid keycode option (e.g. `set t_foo=123`) no longer gives an error.
| * | vim-patch:e06f2b498cccdundargoc2023-12-16
| | | | | | | | | | | | | | | | | | | | | | | | runtime(doc): fix typo in change.txt https://github.com/vim/vim/commit/e06f2b498ccca921f34a1bec4464f042a5a2cabd Co-authored-by: Christian Brabandt <cb@256bit.org>
| * | refactor(defaults): always set options, even if value hasn't changed (#26595)Gregory Anders2023-12-15
| | | | | | | | | | | | | | | | | | | | | | | | Comparing against the old value before setting matched the original C implementation, but there is no reason to use this restriction. In particular, this inhibits using OptionSet to determine when the option was set. If users need to handle a case where the option _changed_, it is easy to do so in an OptionSet autocommand using v:option_new and v:option_old (and friends).
| * | vim-patch:9a775b4a2ae6 (#26588)zeertzjq2023-12-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | runtime(netrw): escape curdir in BrowseUpDir (vim/vim#13681) fixes vim/vim#13678 https://github.com/vim/vim/commit/9a775b4a2ae658e61f9d6582de72ea7a1b241aaa Co-authored-by: Christian Brabandt <cb@256bit.org>
| * | Merge pull request #26579 from gpanders/defer-set-tgcGregory Anders2023-12-15
| |\ \ | | | | | | | | refactor(defaults): defer setting 'termguicolors' until after VimEnter
| | * | refactor(defaults): defer setting 'termguicolors' until after VimEnterGregory Anders2023-12-14
| | | | | | | | | | | | | | | | | | | | This ensures that any OptionSet autocommands will fire when the value is changed.
| | * | fix(termcap): set 'nested' on TermResponse autocommandGregory Anders2023-12-14
| | | |
| * | | vim-patch:3afc9f2556faChristian Clason2023-12-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | runtime(cmake): sync runtime files with upstream (vim/vim#13597) https://github.com/vim/vim/commit/3afc9f2556faf2574d7950d879f2bf61612f3367 Co-authored-by: Eisuke Kawashima <e-kwsm@users.noreply.github.com>
| * | | vim-patch:1c97b5c0c0b4Christian Clason2023-12-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | runtime(vim): Update syntax file, fix missing for highlight (vim/vim#13668) Fix highlighting of :for command. Link the vimFor syntax group to the vimCommand highlight group. Error introduced in commit f686921 https://github.com/vim/vim/commit/1c97b5c0c0b4a60d652b78da4470aeb8a7509700 Co-authored-by: dkearns <dougkearns@gmail.com>
generated by cgit (git 2.34.1) at 2025-05-09 01:26:14 +0000