aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
| * | | | | | feat(vim.deprecate): only issue warning if neovim version is high enoughdundargoc2023-12-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As specified by MAINTAIN.md, features should be soft deprecated at first (meaning no warnings) to give people a chance to adjust. The problem with this approach is that deprecating a feature becomes harder than usual as during the soft deprecation period you need to remember not to issue a warning, and during the hard deprecation period you need to remember to start issuing a warning. This behavior is only enforced if the `plugin` parameter is `nil` as plugins may not want this specific behavior.
| * | | | | | Merge pull request #25528 from bfredl/nocpolispbfredl2023-12-25
| |\ \ \ \ \ \ | | | | | | | | | | | | | | | | refactor(cpoptions): remove 'p'
| | * | | | | | refactor(cpoptions): remove 'p'bfredl2023-12-25
| |/ / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Deleting a cpo flag a day keeps the doctor away We don't need two different ways to indent LISP code
| * | | | | | refactor(drawline): reduce size of wlv.extra[] (#26733)zeertzjq2023-12-25
| | | | | | | | | | | | | | | | | | | | | It's now only used for transchar_hex(), which only needs 11 bytes.
| * | | | | | test(extmarks): improve tests for ui_watched (#26732)zeertzjq2023-12-25
| | | | | | |
| * | | | | | feat(health): make :checkhealth support more split modifiers (#26731)zeertzjq2023-12-25
| | | | | | |
| * | | | | | feat(health): checkhealth buffer can show in a split window (#26714)Pablo Arias2023-12-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | :checkhealth now respects :vertical and :horizontal. For example: :vertical checkhealth foo bar will open the healthcheck buffer in a vertical split.
| * | | | | | build: remove clint checks and style text covered by uncrustifydundargoc2023-12-24
| | | | | | |
| * | | | | | refactor: follow style guidedundargoc2023-12-24
| | | | | | |
| * | | | | | build(deps): bump luajit to HEAD - c525bcb90Christian Clason2023-12-24
| | | | | | |
| * | | | | | fix(treesitter): outdated highlight due to tree with outdated regionJaehwang Jung2023-12-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: A region managed by an injected parser may shrink after re-running the injection query. If the updated region goes out of the range to be parsed, then the corresponding tree will remain outdated, possibly retaining the nodes that shouldn't exist anymore. This results in outdated highlights. Solution: Re-parse an invalid tree if its region intersects the range to be parsed.
| * | | | | | Merge pull request #26642 from famiu/refactor/options/misczeertzjq2023-12-24
| |\ \ \ \ \ \ | | | | | | | | | | | | | | | | refactor(options): miscellanous refactors
| | * | | | | | refactor(options): do bound checking in `validate_num_option()`Famiu Haque2023-12-24
| | | | | | | |
| | * | | | | | refactor(options): remove side effects from `check_num_option_bounds()`Famiu Haque2023-12-24
| | | | | | | |
| | * | | | | | refactor(options): use `OptIndex` for `os_idx`Famiu Haque2023-12-23
| | | | | | | |
| | * | | | | | refactor(options): move some functions from options.c to option.cFamiu Haque2023-12-23
| | | | | | | |
| | * | | | | | refactor(options): restructure functions related to key optionsFamiu Haque2023-12-23
| | | | | | | |
| * | | | | | | refactor: remove os_errmsg and os_msg functionsdundargoc2023-12-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Instead replace them with fprintf and printf.
| * | | | | | | vim-patch:ea9964a36f94Christian Clason2023-12-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Runtime(fortran): updates to indent, syntax and ftplugin (vim/vim#13752) * runtime update fortran.vim Add folding for newer features of Fortran * Runtime Update fortran.vim Add indent support for newer features of Fortran * Runtime Update fortran.vim Add newer features of Fortran to matchit patterns https://github.com/vim/vim/commit/ea9964a36f948c1266d43dd8b3890c6f3bdd243d Co-authored-by: Ajit-Thakkar <142174202+Ajit-Thakkar@users.noreply.github.com>
| * | | | | | | vim-patch:ec97edcbb9f6Christian Clason2023-12-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | runtime(debcontrol): Add loong64 arch (vim/vim#13754) https://github.com/vim/vim/commit/ec97edcbb9f6c0b751b03b981fd8191dbef0a5bb Co-authored-by: James McCoy <jamessan@jamessan.com> Co-authored-by: zhangjialing@loongson.cn <zhangjialing@loongson.cn>
| * | | | | | | refactor: remove CPO_TO_CPO_FLAGS() (#26718)zeertzjq2023-12-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Just pass p_cpo to replace_termcodes() directly. This allows removing option_vars.h from keycodes.h, and also avoids the mistake of passing 0 as cpo_flags.
| * | | | | | | fix(mappings): fix mapset() not replacing map with backslash (#26719)zeertzjq2023-12-23
| |/ / / / / /
| * | | | | | refactor(IWYU): move evalarg_T to eval_defs.h (#26716)zeertzjq2023-12-23
| | | | | | |
| * | | | | | build(nix): update flake.lock (#26702)Jared Baur2023-12-23
| | | | | | | | | | | | | | | | | | | | | updates nixpkgs version to reflect the removal of nvim-client in the build see https://github.com/NixOS/nixpkgs/pull/274865
| * | | | | | refactor(drawline): avoid storing info to draw 'statuscolumn' (#26712)luukvbaal2023-12-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We no longer return to the main loop in win_line() to put column characters on the screen. Simplify and sync statuscolumn drawing logic with that of statusline.
| * | | | | | fix(decor): allow adding providers during redrawLewis Russell2023-12-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes: #26652
| * | | | | | fix(lsp): filetype matching to documentSelector in dynamic capabilities (#25425)Michal Liszcz2023-12-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use the get_language_id client option to resolve the filetype when matching the document selector in a dynamic capability. Co-authored-by: Mathias Fussenegger <f.mathias@zignar.net>
| * | | | | | Merge pull request #26709 from luukvbaal/drawstatuscolzeertzjq2023-12-22
| |\ \ \ \ \ \
| | * | | | | | refactor(drawline): simplify draw_statuscol() and remove draw_state referencesLuuk van Baal2023-12-22
| |/ / / / / /
| * | | | | | Merge pull request #26528 from bfredl/nodrawstatebfredl2023-12-22
| |\ \ \ \ \ \ | | | | | | | | | | | | | | | | refactor(drawline): remove LineDrawState and wlv->saved_n_extra
| | * | | | | | refactor(drawline): remove LineDrawState and wlv->saved_n_extrabfredl2023-12-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We do not need an enum to keep track of what place in win_line() we currently are at. We already have a variable which keeps track where in the code we currently are (and thus what part of the line we are currently rendering), it is called the _program counter_. When we need non-linear or self-referential control-flow anyway for a laugh, we have a mechanism for that, it is called _function calls_. Do not "save" and "restore" the wlv->n_extra state every time the columns are to be drawn. This sort of thing needs to go away. Instead of setting the n_extra variables and then going to the outer while loop, the text in the columns can be rendered by just simply putting the text into the cells of the screen line, right away. Even in nvim this can be tricky sometimes, luckily we can use function calls to abstract this logic, which means that this handy data structure called the _call stack_ is handling saving away state temporarily, and restoring it back when we need it again. Lastly, but not least, as we now have direct control how signs are rendered, these can be stored as schar_T[2] and be directly put on screen as such.
| * | | | | | | refactor(lsp): move glob parsing to util (#26519)Steven Arcangeli2023-12-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | refactor(lsp): move glob parsing to vim.glob Moving the logic for using vim.lpeg to create a match pattern from a glob into `vim.glob`. There are several places in the LSP spec that use globs, and it's very useful to have glob matching as a generally-available utility.
| * | | | | | | feat(lsp): add type annotations for lsp.util.locations_to_items (#26694)Mathias Fußenegger2023-12-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: luals reported many warnings Solution: Add type annotations
| * | | | | | | 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>
| * | | | | | | refactor(IWYU): add "private" pragma to more generated headers (#26706)zeertzjq2023-12-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | "export" only prevents IWYU from adding these headers if the headers that export them are included, while "private" ensures that IWYU never adds these headers.
| * | | | | | | refactor(options): generate BV_ and WV_ constants (#26705)zeertzjq2023-12-22
| | | | | | | |
| * | | | | | | 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>
| * | | | | | | refactor: run IWYU on entire repodundargoc2023-12-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reference: https://github.com/neovim/neovim/issues/6371.
| * | | | | | | fix(build): teach cmake about vvarsLewis Russell2023-12-21
| | | | | | | |
| * | | | | | | 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.
| * | | | | | | fix(column): avoid exceeding configured 'signcolumn' widthLuuk van Baal2023-12-21
| |/ / / / / /
| * | | | | | 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.
| * | | | | | refactor(IWYU): move decor provider types to decoration_defs.h (#26692)zeertzjq2023-12-21
| | | | | | |