aboutsummaryrefslogtreecommitdiff
path: root/runtime
Commit message (Collapse)AuthorAge
* 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
|
* fix(lsp): fix infinite loop in resolved_capabilities deprecation message ↵ii142022-04-30
| | | | | (#18333) Co-authored-by: ii14 <ii14@users.noreply.github.com>
* fix(lsp): handle textDocumentSync.save bool capability (#18332)Mathias Fußenegger2022-04-30
| | | Follow up to https://github.com/neovim/neovim/pull/17814
* 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.
* | vim-patch:8.2.4849: Gleam filetype not detected (#18326)Christian Clason2022-04-30
| | | | | | | | | | | | Problem: Gleam filetype not detected. Solution: Add a pattern for Gleam files. (Mathias Jean Johansen, closes vim/vim#10326) https://github.com/vim/vim/commit/917c32c4f75351061a773cd5bc5b6f42c7d10e62
* | 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
|
* fix(handlers): more specific error messages (#16772)kylo2522022-04-30
| | | | Specify which message, or request, was last received in case of an error instead of the same generic message
* 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(lsp): show feedback on empty hover response (#18308)Mathias Fußenegger2022-04-29
| | | | Without any feedback it gives the impression that the language server is not working properly, which isn't the case.
* 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(checkhealth): check for slow shell #17829Philip Linell2022-04-26
| | | | | | | | | | Problem: I had some issues where multiple plugins (vim-fzf and fugitive) was slow because of my `.zshenv`. Solution: Check shell performance in :checkhealth. Co-authored-by: Justin M. Keyes <justinkz@gmail.com>
* fix(lsp): fix unnecessary buffers being added on empty diagnostics (#18275)ii142022-04-26
| | | | | Some language servers send empty `textDocument/publishDiagnostics` messages after indexing the project with URIs corresponding to unopened buffers. This commit guards against opening buffers corresponding to empty diagnostics.
* 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
* vim-patch:8.2.4826: .cshtml files are not recognized (#18259)Christian Clason2022-04-25
| | | | | Problem: .cshtml files are not recognized. Solution: Use html filetype for .cshtml files. (Julien Voisin, closes vim/vim#10212) https://github.com/vim/vim/commit/1f435dafff2452e0b55d1ca457ce7402e526e92a
* 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.
* revert: "man.vim: Ensure 'modifiable' in man#init_pager" #17791dundargoc2022-04-25
| | | | | | | | | | | | | This reverts commit 526798a941b4cf80fd1f128b40e51fb47c77b654. This will make man filetype not modifiable by default, as it is the superior behavior in my opinion. More importantly, also make it possible for a user to modify man filetypes by adding `set modifiable` in `~/.config/nvim/ftplugin/man.vim` or its equivalent. ref #11450 closes #17595 Co-authored-by: Javier López <graulopezjavier@gmail.com>
* 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
* fix(ftdetect): source plugins in autogroup (#18237)Christian Clason2022-04-23
| | | In `filetype.lua`, source runtime `ftdetect` scripts within the `filetypedetect` augroup, same as `filetype.vim` (and only do so if `g:did_load_ftdetect` does not exist).
* fix(lua): don't mutate opts parameter of vim.keymap.del (#18227)Andrey Mishchenko2022-04-23
| | | | | | `vim.keymap.del` takes an `opts` parameter that lets caller refer to and delete buffer-local mappings. For some reason the implementation of `vim.keymap.del` mutates the table that is passed in, setting `opts.buffer` to `nil`. This is wrong and also undocumented.
* fix(treesitter): create new parser if language is not the same as cached ↵Chinmay Dalal2022-04-22
| | | | parser (#18149)
* Merge pull request #18211 from clason/update-inspectbfredl2022-04-22
|\ | | | | chore: update inspect.lua to 3.1.3
| * chore: update inspect.lua to 3.1.3Christian Clason2022-04-21
| |
* | 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
|
* Merge pull request #18185 from clason/vim-8.2.4781Christian Clason2022-04-20
|\ | | | | vim-patch:8.2.{4781,4793}: maxima files are not recognized
| * vim-patch:8.2.4793: recognizing Maxima filetype even though it might be anotherChristian Clason2022-04-20
| | | | | | | | | | | | Problem: Recognizing Maxima filetype even though it might be another. Solution: Remove *.mc and *.dem patterns from Maxima files https://github.com/vim/vim/commit/928a13135629fa8e73796760077b1b877918a080
| * vim-patch:8.2.4781: Maxima files are not recognizedChristian Clason2022-04-20
| | | | | | | | | | | | Problem: Maxima files are not recognized. Solution: Add patterns to detect Maxima files. (Doron Behar, closes vim/vim#10211) https://github.com/vim/vim/commit/d0a20c9d111da75febb60ffee2e15f727ab6a5ad
* | 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>
* | fix(lsp): unify progress message handling (#18040)runiq2022-04-20
| | | | | | | | | | | | | | | | | | | | | | The LSP progress handler would put non-progress messages (such as from clangd or pyls; not part of the LSP spec) directly into `client.messages`, while `vim.lsp.util.get_progress_messages()` would try to fetch them from `client.messages.messages` instead (and come up empty everytime). This would result in these messages never being cleaned up by `get_progress_messages()`. This commit fixes that by treating those messages like show-once progress messages (by setting `done=true` immediately).
* | fix(diagnostic): use nvim_exec_autocmds to trigger DiagnosticChanged (#18188)Gregory Anders2022-04-20
| | | | | | | | | | Use nvim_exec_autocmds to issue the DiagnosticChanged autocommand, rather than nvim_buf_call, which has some side effects when drawing statuslines.
* | 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
| |
* | vim-patch:8.2.4790: lilypond filetype not recognized (#18174)Christian Clason2022-04-20
| | | | | | | | | | Problem: Lilypond filetype not recognized. Solution: Add patterns for lilypond. (Doug Kearns) https://github.com/vim/vim/commit/c448e9c95089b5e7170a0dd36635a226c5eb5b1c
* | 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.
generated by cgit (git 2.34.1) at 2025-06-24 19:20:39 +0000