aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Add support in Neovim for f38-f63 key bindings.newfeaturesJosh Rahm2021-10-07
| | | | | These bindings are generally accesses with <M-Fx> key presses.
* Change the Popup menu omnihighlight to use %#<hl># format.Josh Rahm2021-10-05
| | | | | Before it used \x1b<hl>], but this is more consistent with the rest of Vim.
* Enable multibyte registers in VimL.Josh Rahm2021-10-05
| | | | | | This allows users to execute commands like: let @λ = 'new register content.'
* Add documentation for the userregfun setting.Josh Rahm2021-10-05
|
* Add user-registers for arbitrary registers.Josh Rahm2021-10-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This allows users to define behaviors for arbitrary registers. These registers can be any character including multibyte characters. This means that any character may be used as a register and if that register is not a builtin register, it will defer to a user-defined vimscript function for behavior. This is done throw an option called 'userregfun' The function that 'userregfun' defines is a function that takes 3 arguments: action - Either set to "put" or "yank" register - The character representing the register. content - If the action is "yank" this string contains the content yanked. Multibyte registers are still broken for expressions. So while let @&=xyz Works as expected, let @λ=xyz will still throw a parse error.
* Add colorable popupmenu.Josh Rahm2021-10-05
| | | | This is done with using embedded tags with the format YourHighlight].
* Add colorcol character documentation.Josh Rahm2021-10-05
|
* Move colorcolumn character option to fillchars.Josh Rahm2021-10-05
| | | | listchars is not the right place for it.
* Add a colorcolumn character option.Josh Rahm2021-10-05
| | | | | | | | | | This option allows a character to be displayed in the colorcolumn. This allows the colorcolumn ot have a traditional line if the colorcolumn character is set to a vertical line '│' or even a series of dots for a ':'. The option is a part of the 'listchars' setting under the name 'colorcol'. So 'set listchars=colorcol:│' will work.
* Add a check to the gen_options.lua script to ensure the options are well ↵Josh Rahm2021-10-05
| | | | | | | | | | | | ordered. (Neo)Vim uses a jump table based on the first character of the option's name. This means for it to work all options with the same first character must be together. If this is violated, some options may seem to disappear, which can sometimes happen during merges if not careful. This commit adds a check to the gen_options.lua script so the build will fail if this constraint is violated.
* Add the ability to title floating windows.Josh Rahm2021-10-05
| | | | | | | | | | | | | The window title is set using the {title} key on the FloatConfig. The window title allows for 3 different positions as defined by the {title_position} key in the FloatConfig: - left - center - right The title also supports StatusLine-style highlighting using the %#<HL># keys.
* build(deps): bump luarocks to 3.7.0 #15740Christian Clason2021-09-22
| | | | | | | | | | | Besides bugfixes, this brings `XDG_*` compliance and improved robustness, especially for network errors. See https://github.com/luarocks/luarocks/blob/master/CHANGELOG.md - fixup: set LIBUV_LIBDIR to workaround https://github.com/luarocks/luarocks/commit/83126ba324846b754ffc5e0345341f01262b3f86 - https://github.com/luarocks/luarocks/issues/1214 - https://github.com/luarocks/luarocks/pull/1355
* feat(diagnostic): allow customized diagnostic messages (#15742)Gregory Anders2021-09-22
| | | | Provide a 'format' option for virtual text and floating window previews that allows the displayed text of a diagnostic to be customized.
* Merge pull request #15739 from clason/luv-bumpJames McCoy2021-09-22
|\
| * fix(build): call find_package(Threads) before using its variablesJames McCoy2021-09-21
| |
| * chore(deps): bump libuv and luv to 1.42.0Christian Clason2021-09-21
| |
* | Merge pull request #14115 from mfussenegger/lsp-commandsMichael Lingelbach2021-09-22
|\ \ | | | | | | lsp: Add a registry for client side code action commands
| * | feat(lsp): add a registry for client side code action commandsMathias Fussenegger2021-09-20
| | | | | | | | | | | | | | | This builds on https://github.com/neovim/neovim/pull/14112 and closes https://github.com/neovim/neovim/issues/12326
| * | feat(lsp): include original request params in handler ctxMathias Fussenegger2021-09-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is mostly motivated by https://github.com/neovim/neovim/issues/12326 Client side commands might need to access the original request parameters. Currently this is already possible by using closures with `vim.lsp.buf_request`, but the global handlers so far couldn't access the request parameters.
* | | docs: .git-blame-ignore-revs #15653Justin M. Keyes2021-09-22
| | |
* | | refactor: format with uncrustify #15741dundargoc2021-09-22
| | |
* | | vim-patch:34cc7d8c034f #15753Christian Clason2021-09-22
| | | | | | | | | | | | Update runtime files https://github.com/vim/vim/commit/34cc7d8c034f2bc5b57455577051db8d72e2b87c
* | | Merge pull request #15717 from gpanders/diagnostic-include-sourceMichael Lingelbach2021-09-21
|\ \ \ | | | | | | | | feat(diagnostic): add option to include diagnostic source
| * | | refactor(diagnostic): remove get_virt_text_chunks()Gregory Anders2021-09-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This function isn't compatible with including diagnostic sources when "source" is "if_many" since it only has access to diagnostics for a single line. Rather than having an inconsistent or incomplete interface, make this function private. It is still exported as part of the module for backward compatibility with vim.lsp.diagnostics, but it can eventually be made into a local function.
| * | | feat(diagnostic): add option to include diagnostic sourceGregory Anders2021-09-21
|/ / / | | | | | | | | | | | | Add an option to virtual text display and floating window previews to include diagnostic source in the diagnostic message.
* | | fix(diagnostic): preserve fields from LSP diagnostics via user_data (#15735)masterGregory Anders2021-09-21
| | | | | | | | | * preserve fields from LSP diagnostics via adding a user_data table to the diagnostic, which can hold arbitrary data in addition to the lsp diagnostic information.
* | | fix(lsp): update lsp-handler signature in call_hierarchy (#15738)Mathias Fußenegger2021-09-21
| | | | | | | | | | | | | | | | | | | | | | | | This fixes the handler signature and also prevents n+1 requests firing if there are multiple clients. (The first `prepareCallHierarchy` handler is called once per client, each invocation used `buf_request` to make more requests using *all* clients)
* | | ci(PVS): PVS/V009: add required header #15751dundargoc2021-09-21
| | |
* | | fix(startup): init.lua: set $MYVIMRC to absolute path #15748Justin M. Keyes2021-09-21
| | | | | | | | | | | | | | | | | | - main.c: remove os_setenv("MYVIMRC",…), it is already done by do_source(). - This also sets $MYVIMRC to a full (absolute) path. - code cleanup.
* | | Merge pull request #15745 from e-kwsm/MakefileJames McCoy2021-09-21
|\ \ \ | |_|/ |/| | build: enhance Makefile
| * | build: enhance MakefileEisuke Kawashima2021-09-21
|/ / | | | | | | | | | | | | - fix regression where `-j` is not passed to ninja (39c886551bf8323b63938f5dee5beb650c61f02b, #15708) - enable to pass `-l` (load) to ninja as well - s/BUILD_TYPE/CMAKE_GENERATOR/
* | Merge pull request #15743 from jamessan/libuv-threadsJames McCoy2021-09-20
|\ \ | |/ |/| build: Add ${CMAKE_THREAD_LIBS_INIT} to LIBUV_LIBRARIES
| * build: add ${CMAKE_THREAD_LIBS_INIT} to LIBUV_LIBRARIESJames McCoy2021-09-20
|/ | | | | | | This is a workaround for not yet having fully correct Find* cmake modules for static builds. https://github.com/Tronic/cmake-modules/issues/3#issuecomment-624469020
* fix(diagnostic): clamp line numbers in display layer (#15729)Gregory Anders2021-09-20
| | | | | | Some parts of LSP need to use cached diagnostics as sent from the LSP server unmodified. Rather than fixing invalid line numbers when diagnostics are first set, fix them when they are displayed to the user (e.g. in show() or one of the get_next/get_prev family of functions).
* refactor: reformat with uncrustify #15736dundargoc2021-09-20
| | | | * fix function parameter comments * remove space after star in function names
* fix(inccommand): ignore trailing commands only for *previewed* command #15638itchyny2021-09-20
| | | | | | | | Since the `State` is global, other scripts are unexpectedly affected during the 'inccommand' preview. This commit introduces a new flag for `do_cmdline`, in order to ignore trailing '|'-separated commands only for the command invoking the preview. fix #8796, update #7494
* refactor: format with uncrustify #15726dundargoc2021-09-20
|
* Merge #15727 build(lint): check scripts/*.luaJustin M. Keyes2021-09-19
|\
| * build(lint): commit linterJustin M. Keyes2021-09-19
| |
| * build(lint): check scripts/*.luaJustin M. Keyes2021-09-19
|/
* refactor(Makefile): use built-in make commands #15708kylo2522021-09-19
| | | | | | | | | | | | | | | | | | | Changes to the main Makefile: - add `MAKEFILE_PATH` and `MAKEFILE_DIR` that are set with native commands - add `NVIM_PRG` - rename `BUILD_TYPE` to `CMAKE_GENERATOR` to align with CMake naming - remove the misleading `BUILD_CMD` and use `BUILD_TOOL` instead Add the following phony target to quickly test the changes ```make debug-print: @echo makefile path: $(MAKEFILE_PATH) @echo makefile dir: $(MAKEFILE_DIR) @echo build dir: $(BUILD_DIR) @echo cmake generator tool: $(CMAKE_GENERATOR) @echo build-tool: $(BUILD_TOOL) @echo nvim-prg: $(NVIM_PRG) ```
* feat(diagnostic): match(), tolist(), fromlist() #15704Gregory Anders2021-09-19
| | | | | | * feat(diagnostic): add vim.diagnostic.match() Provide vim.diagnostic.match() to generate a diagnostic from a string and a Lua pattern. * feat(diagnostic): add tolist() and fromlist()
* refactor: format with uncrustify #15722dundargoc2021-09-19
|
* build(lint): commit linter #15725Justin M. Keyes2021-09-19
| | | | | | | | | | | | | | | | | | | | | | | | | Example test failure: $ nvim -es +"lua require('scripts.lintcommit')._test()" [ FAIL ]: expected=true, got=false input: ":no type before colon 1" [ FAIL ]: expected=true, got=false input: "ci: tab after colon" Example main({trace=true}) output: $ nvim -es +"lua require('scripts.lintcommit').main()" run: { "git", "branch", "--show-current" } run: { "git", "merge-base", "origin/master", "master" } run: { "git", "merge-base", "upstream/master", "master" } run: { "git", "rev-list", "89db07556dbdce97c0c150ed7e47d80e1ddacad3..master" } run: { "git", "show", "-s", "--format=%s", "d2e6d2f5fc93b6da3c6153229135ba2f0b24f8cc" } Invalid commit message: "buildlint): commit linter #15620" Commit: d2e6d2f5fc93b6da3c6153229135ba2f0b24f8cc Invalid commit type "buildlint)". Allowed types are: { "build", "ci", "docs", "feat", "fix", "perf", "refactor", "revert", "test", "chore", "vim-patch" } See also: https://github.com/neovim/neovim/blob/master/CONTRIBUTING.md#commit-messages https://www.conventionalcommits.org/en/v1.0.0/
* Merge pull request #15630 from zeertzjq/vim-8.2.3424Jan Edmund Lazo2021-09-19
|\ | | | | vim-patch:8.1.{1071,1078,1079,1110},8.2.{2640,3424,3425,3437}
| * vim-patch:8.2.3437: compiler warnings for 32/64 bit usagezeertzjq2021-09-19
| | | | | | | | | | | | Problem: Compiler warnings for 32/64 bit usage. Solution: Add type casts. (Mike Williams, closes vim/vim#8870) https://github.com/vim/vim/commit/f5785cf0592626ec17676e814d3ba58f5123bcda
| * vim-patch:8.2.3425: warning for using uninitialized variablezeertzjq2021-09-19
| | | | | | | | | | | | Problem: Warning for using uninitialized variable. Solution: Initialize it. (John Marriott) https://github.com/vim/vim/commit/56e14698b45a9c4ef8fa65c55c9bfe86fbb3d6bf
| * vim-patch:8.2.3424: a sequence of spaces is hard to see in list modezeertzjq2021-09-19
| | | | | | | | | | | | Problem: A sequence of spaces is hard to see in list mode. Solution: Add the "multispace" option to 'listchars'. (closes vim/vim#8834) https://github.com/vim/vim/commit/f14b8ba1373f569705cb80419248054100b02360
| * vim-patch:8.2.2640: screenstring() returns non-existing composing characterszeertzjq2021-09-19
| | | | | | | | | | | | Problem: screenstring() returns non-existing composing characters. Solution: Only use composing characters if there is a base character. https://github.com/vim/vim/commit/f1387285e2ebe5cb3688d729fc6fd01a169a76c1
| * vim-patch:8.1.1110: composing chars on space wrong when 'listchars' is setzeertzjq2021-09-19
| | | | | | | | | | | | | | Problem: Composing chars on space wrong when 'listchars' is set. Solution: Do not use "space" and "nbsp" entries of 'listchars' when there is a composing character. (Yee Cheng Chin, closes vim/vim#4197) https://github.com/vim/vim/commit/e5e4e22c1c15c8c22b14935affe969569acc8df9
generated by cgit (git 2.34.1) at 2025-04-29 09:03:57 +0000