aboutsummaryrefslogtreecommitdiff
path: root/runtime/doc
Commit message (Collapse)AuthorAge
...
| * | feat(server): set $NVIM, unset $NVIM_LISTEN_ADDRESS #11009Justin M. Keyes2022-05-03
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | PROBLEM ------------------------------------------------------------------------ $NVIM_LISTEN_ADDRESS has conflicting purposes as both a parameter ("the current process should listen on this address") and a descriptor ("the current process is a child of this address"). This contradiction means the presence of NVIM_LISTEN_ADDRESS is ambiguous, so child Nvim always tries to listen on its _parent's_ socket. This is the cause of lots of "Failed to start server" spam in our test/CI logs: WARN 2022-04-30… server_start:154: Failed to start server: address already in use: \\.\pipe\nvim-4480-0 WARN 2022-04-30… server_start:154: Failed to start server: address already in use: \\.\pipe\nvim-2168-0 SOLUTION ------------------------------------------------------------------------ 1. Set $NVIM to the parent v:servername, *only* in child processes. - Now the correct way to detect a "parent" Nvim is to check for $NVIM. 2. Do NOT set $NVIM_LISTEN_ADDRESS in child processes. 3. On startup if $NVIM_LISTEN_ADDRESS exists, unset it immediately after server init. 4. Open a channel to parent automatically, expose it as v:parent. Fixes #3118 Fixes #6764 Fixes #9336 Ref https://github.com/neovim/neovim/pull/8247#issuecomment-380275696 Ref #8696
| * refactor(ui): simplify stdin handlingbfredl2022-05-02
| |
| * docs: syntax is enabled by default (#17637)Christian Clason2022-05-01
| | | | | | `:syntax enable` is no longer necessary (and may even be harmful). Do not recommend it in `usr_05.txt` and `usr_06.txt`, and mention the new default in `syntax.txt`.
| * docs(api): more API attributes #18336ii142022-04-30
| |
| * docs: move "hl-VertSplit" to deprecated.txt #18328Famiu Haque2022-04-30
| |
| * Merge pull request #18231 from famiu/feat/api/parse_cmdlinebfredl2022-04-30
| |\ | | | | | | feat(api): `nvim_parse_cmd`
| | * feat(api): add `nvim_parse_cmdline`Famiu Haque2022-04-30
| | | | | | | | | | | | Adds an API function to parse a command line string and get command information from it.
| * | feat(lsp): add async option to vim.lsp.buf.format (#18322)Mathias Fußenegger2022-04-30
| |/ | | | | | | | | | | | | | | Deprecates the existing `vim.lsp.buf.formatting` function. With this, `vim.lsp.buf.format` will replace all three: - vim.lsp.buf.formatting - vim.lsp.buf.formatting_sync - vim.lsp.buf.formatting_seq_sync
| * feat(lsp): add vim.lsp.buf.format (#18193)Michael Lingelbach2022-04-30
| |
| * chore(lsp): remove capabilities sanitization (#17814)Michael Lingelbach2022-04-30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * feat(lsp)!: remove capabilities sanitization Users must now access client.server_capabilities which matches the same structure as the protocol. https://microsoft.github.io/language-server-protocol/specification client.resolved_capabilities is no longer used to gate capabilities, and will be removed in a future release. BREAKING CHANGE Co-authored-by: Mathias Fussenegger <f.mathias@zignar.net>
| * feat(lsp): options to filter and auto-apply code actions (#18221)Fredrik Ekre2022-04-30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Implement two new options to vim.lsp.buf.code_action(): - filter (function): predicate taking an Action as input, and returning a boolean. - apply (boolean): when set to true, and there is just one remaining action (after filtering), the action is applied without user query. These options can, for example, be used to filter out, and automatically apply, the action indicated by the server to be preferred: vim.lsp.buf.code_action({ filter = function(action) return action.isPreferred end, apply = true, }) Fix #17514.
| * feat(mappings): do not simplify the rhs of a mappingzeertzjq2022-04-29
| |
| * feat(mappings): do not replace existing mapping for simplified formzeertzjq2022-04-29
| |
| * test: revert test and doc changes from #6724, add a test for #6716zeertzjq2022-04-29
| | | | | | | | Multi-char 'pastetoggle' now works without breaking character-find.
| * vim-patch:8.2.0867: using \{xxx} for encoding a modifier is not nicezeertzjq2022-04-29
| | | | | | | | | | | | | | | | | | Problem: Using \{xxx} for encoding a modifier is not nice. Solution: Use \<*xxx> instead, since it's the same as \<xxx> but producing a different code. https://github.com/vim/vim/commit/fccd93f0917234b962ce07d1df3adf9d7105936f Use this notation in langmap_spec.
| * vim-patch:8.2.0855: GUI tests fail because the test doesn't use a modifierzeertzjq2022-04-29
| | | | | | | | | | | | | | | | Problem: GUI tests fail because the test doesn't use a modifier. Solution: Add "\{xxx}" to be able to encode a modifier. https://github.com/vim/vim/commit/ebe9d34aa07037cff2188a8dd424ee1f59cbb0bf Change macros to enums to use them in unit tests.
| * feat(edit): insert an unsimplified key using CTRL-SHIFT-Vzeertzjq2022-04-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This marks the following Vim patches as ported: vim-patch:8.1.2333: with modifyOtherKeys CTRL-^ doesn't work Problem: With modifyOtherKeys CTRL-^ doesn't work. Solution: Handle the exception. https://github.com/vim/vim/commit/828ffd596394f714270a01a55fc3f949a8bd9b35 vim-patch:8.1.2350: other text for CTRL-V in Insert mode with modifyOtherKeys Problem: Other text for CTRL-V in Insert mode with modifyOtherKeys. Solution: Convert the Escape sequence back to key as if modifyOtherKeys is not set, and use CTRL-SHIFT-V to get the Escape sequence itself. (closes vim/vim#5254) https://github.com/vim/vim/commit/fc4ea2a72d36de1196a3ce17352e72f8fe90f4bb vim-patch:8.2.2084: CTRL-V U doesn't work to enter a Unicode character Problem: CTRL-V U doesn't work to enter a Unicode character when modifyOtherKeys is effective. (Ken Takata) Solution: Add a flag to get_literal() for the shift key. (closes vim/vim#7413) https://github.com/vim/vim/commit/0684e36a7ee0743f2889698fb8e0e14f7acae423 Omit getcmdkeycmd() change as it depends on Vim patch 8.2.2062, which may introduce a potential breakage.
| * vim-patch:ce001a337e28 (#18287)Christian Clason2022-04-27
| | | | | | | | | | | | Update runtime files https://github.com/vim/vim/commit/ce001a337e28fa368f40ac6422835d730fb8ebb1 also add `vimStdPlugin` keywords missing from previous updates
| * refactor(terminal)!: drop winpty, require Windows 10 #18253erw72022-04-26
| | | | | | | | | | | | | | | | | | | | | | Problem: winpty is only needed for Windows 8.1. Removing it reduces our build and code complexity. Solution: - Remove winpty. - Require Windows 10. closes #18252
| * feat(tui): query terminal for CSI u support (#18181)Gregory Anders2022-04-25
| | | | | | | | | | | | On startup query the terminal for CSI u support and enable it using the escape sequence from kitty's progressive enhancement protocol [1]. [1]: https://sw.kovidgoyal.net/kitty/keyboard-protocol/
| * vim-patch:8.2.4760: using matchfuzzy() on a long list can take a whilezeertzjq2022-04-26
| | | | | | | | | | | | | | Problem: Using matchfuzzy() on a long list can take a while. Solution: Add a limit to the number of matches. (Yasuhiro Matsumoto, closes vim/vim#10189) https://github.com/vim/vim/commit/9029a6e9931eede1d44f613687a2c01b9fe514ec
| * fix: show autocmd output when F is in shortmess (#18251)Gregory Anders2022-04-25
| | | | | | | | | | | | | | | | | | | | | | The default value of including F in 'shortmess' has the unfortunate side effect of hiding output from autocommands. This is a common source of confusion and often leads people to think their autocommands are not working when they are. There is a small snippet in the docs for 'shortmess' indicating that the F flag suppresses autocmd output, but it's not easy to find if you don't already know to look for it. This commit removes that behavior of the F flag to make it only suppress file info when opening a new file.
| * docs: clarify enhanced modifiers, SHIFT usage #18124Joel Bradshaw2022-04-24
| | | | | | | | Co-authored-by: Justin M. Keyes <justinkz@gmail.com> Co-authored-by: zeertzjq <zeertzjq@outlook.com>
| * docs: make docstring consistent with parameters #18178dundargoc2022-04-23
| | | | | | Closes: https://github.com/neovim/neovim/issues/12691
| * docs(lua): explain and link to lua patterns (#18206)Christian Clason2022-04-21
| | | | | | also correct explanation of when it's allowed to omit parens in Lua function calls
| * docs: vim.keymap.set can specify buffer as an optionatusy2022-04-21
| |
| * docs(filetype): proper example for did_load_filetypes (#18191)Christian Clason2022-04-20
| |
| * docs(api): add example showing necessity to wrap callback function (#18179)Mathias Fußenegger2022-04-20
| | | | | | | | | | | | | | Some people ran into issues trying to use `callback = myluafun` because of the event data payload. Co-authored-by: Gregory Anders <8965202+gpanders@users.noreply.github.com>
| * Merge pull request #18145 from bfredl/term_optbfredl2022-04-20
| |\ | | | | | | feat(api): allow remote UI to set terminal options
| | * feat(api): ui options relevant for remote TUIhlpr982022-04-17
| | |
| * | Merge pull request #18157 from famiu/feat/undo!bfredl2022-04-19
| |\ \ | | | | | | | | feat: add `undo!`
| | * | feat: add `undo!`Famiu Haque2022-04-20
| | | | | | | | | | | | | | | | Allows using `undo!` to undo changes and remove them from the undo-tree. Can only be used for moving backwards in the same undo branch.
| * | | Merge pull request #18081 from famiu/feat/highlight/cursearchbfredl2022-04-19
| |\ \ \ | | |/ / | |/| | feat(highlight): implement CurSearch highlight
| | * | feat(highlight): implement CurSearch highlightFamiu Haque2022-04-17
| | |/ | | | | | | | | | Adds a `CurSearch` highlight group to highlight the current search result under the cursor.
| * | vim-patch:75ab590f8504 (#18170)Christian Clason2022-04-19
| | | | | | | | | | | | | | | | | | Update runtime files https://github.com/vim/vim/commit/75ab590f8504a8912ca0b8c58f6b897bb7a34f07 omit builtin.txt change to `expand()` (depends on 8.2.4726)
| * | docs(terminal): correct sentence on how to enter terminal mode (#18146)dundargoc2022-04-18
| |/ | | | | `o`/`O` is not supported for terminal mode
| * docs: typo fixes (#17859)dundargoc2022-04-15
| | | | | | | | | | | | | | | | | | | | Co-authored-by: Elias Alves Moura <eliamoura.alves@gmail.com> Co-authored-by: venkatesh <shariharanvenkatesh@gmail.com> Co-authored-by: zeertzjq <zeertzjq@outlook.com> Co-authored-by: Vikas Raj <24727447+numToStr@users.noreply.github.com> Co-authored-by: Steve Vermeulen <sfvermeulen@gmail.com> Co-authored-by: Evgeni Chasnovski <evgeni.chasnovski@gmail.com> Co-authored-by: rwxd <rwxd@pm.me> Co-authored-by: casswedson <58050969+casswedson@users.noreply.github.com>
| * vim-patch:8.2.4747: no filetype override for .sys files (#18105)Christian Clason2022-04-13
| | | | | | | | | | Problem: No filetype override for .sys files. Solution: Add g:filetype_sys. (Patrick Meiser-Knosowski, closes vim/vim#10181) https://github.com/vim/vim/commit/f420ff2440a009acd9573fdb6ad6d53509d78009
| * Merge pull request #15491 from Diomendius/lua_docsGregory Anders2022-04-13
| |\ | | | | | | docs(lua): fix, clarify Lua require() docs
| | * docs(lua): further improve Lua require() docsDiomendius2021-11-22
| | | | | | | | | | | | | | | Change docs to reflect recent changes to require() search order and add info on `.` in module names and search order for shared library modules.
| | * docs(lua): fix, clarify Lua require() docsDiomendius2021-11-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | Corrects lua.txt help file to say that require() searches runtimepath and loads the first module found, not the last. Also adds additional clarification on require() and module search order. Closes #15480
| * | vim-patch:partial:a2baa73d1d33zeertzjq2022-04-12
| | | | | | | | | | | | | | | | | | | | | Update runtime files. https://github.com/vim/vim/commit/a2baa73d1d33014adea0fd9567949089ca21a782 This only includes changes to docs of digraph functions.
| * | vim-patch:8.2.3226: new digraph functions use old naming schemezeertzjq2022-04-12
| | | | | | | | | | | | | | | | | | Problem: New digraph functions use old naming scheme. Solution: Use the digraph_ prefix. (Hirohito Higashi, closes vim/vim#8580) https://github.com/vim/vim/commit/29b857150c111a455f1a38a8f748243524f692e1
| * | vim-patch:8.2.3184: cannot add a digraph with a leading spacezeertzjq2022-04-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Cannot add a digraph with a leading space. It is not easy to list existing digraphs. Solution: Add setdigraph(), setdigraphlist(), getdigraph() and getdigraphlist(). (closes vim/vim#8580) https://github.com/vim/vim/commit/6106504e9edc8500131f7a36e59bc146f90180fa Use GA_APPEND_VIA_PTR in registerdigraph(). Use tv_list_append_*() in getdigraphlist_appendpair(). Put the error messages in digraph.c. E196 is N/A. Remove mentions about 'encoding' being non-Unicode. Nvim doesn't support setting encoding=japan, so skip a test.
| * | vim-patch:8.2.4713: plugins cannot track text scrollingzeertzjq2022-04-12
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Plugins cannot track text scrolling. Solution: Add the WinScrolled event. (closes vim/vim#10102) https://github.com/vim/vim/commit/0937182d49fa8db50cec42785f22f1031760a0bd Skip User event in autocmd.txt, not needed unless #10689 is reverted.
| * | docs(term.txt): add documentation about TUI input (#18072)zeertzjq2022-04-11
| | |
| * | docs: update dev-api to include "create"Gregory Anders2022-04-10
| | |
| * | refactor!: rename nvim_add_user_command to nvim_create_user_commandGregory Anders2022-04-10
| | |
| * | feat(events): support SIGWINCH for Signal event #18029Loong Wang2022-04-10
| | | | | | | | | closes #15411
| * | docs: remove mentions of removed flag '#' in 'cpoptions' (#18064)UnkwUsr2022-04-10
| | |
generated by cgit (git 2.34.1) at 2025-07-03 01:00:22 +0000