aboutsummaryrefslogtreecommitdiff
path: root/runtime
Commit message (Collapse)AuthorAge
...
| * | | treesitter: add some documentation for parsersThomas Vigouroux2020-06-29
| | | |
| * | | treesitter: add set_included_ranges to the parserThomas Vigouroux2020-06-29
| | | | | | | | | | | | | | | | This is the first step towards language injection using treesitter.
* | | | doc: fix wordcount descriptionMatthieu Coudron2020-06-29
| | | | | | | | | | | | | | | | | | | | was fixed in vim patch c572da5f67aa5cdbbc127fc6f1d0a42e38468325 and forgot in corresponding vim patch 8c3377ee76e5cc4f5a4228f216bde1d03b496d69.
* | | | LSP: Set current name as default rename text (#12553)cbarrete2020-06-27
| | | | | | | | | | | | | | | | | | | | | | | | Since we don't know what the server considers to be a symbol, `cword` is the best bet in most cases. Co-authored-by: Cédric Barreteau <>
* | | | Merge pull request #12252 from dlukes/formatting-syncHirokazu Hata2020-06-27
|\ \ \ \ | |_|/ / |/| | |
| * | | lsp: Add sync variant of LSP formattingDavid Lukes2020-06-22
| | | | | | | | | | | | | | | | | | | | Also, factor out a `vim.lsp.util.get_effective_tabstop()` helper and add tests for it.
* | | | Merge pull request #12133 from bradking/syntax-foldJames McCoy2020-06-24
|\ \ \ \
| * | | | vim-patch:8.2.0865 syntax: Add command to control how foldlevel is computedBrad King2020-06-23
| | |/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Syntax foldlevel is taken from the start of the line. Solution: Add ":syn foldlevel" to be able to use the minimal foldlevel in the line. https://github.com/vim/vim/commit/e35a52aee718c881bdfa69a47a1068df6ab6c60a With `foldmethod=syntax` the foldlevel of a line is computed based on syntax items on the line. Previously we always used the level of the syntax item containing the start of the line. This works well in cases such as: if (...) { ... } else if (...) { ... } else { ... } which folds like this: +--- 3 lines: if (...) {--------------------------- +--- 3 lines: else if (...) {---------------------- +--- 3 lines: else {------------------------------- However, the code: if (...) { ... } else if (...) { ... } else { ... } folds like this: +--- 7 lines: if (...) {--------------------------- We can make the latter case fold like this: +--- 2 lines: if (...) {--------------------------- +--- 2 lines: } else if (...) {-------------------- +--- 3 lines: } else {----------------------------- by choosing on each line the lowest fold level that is followed by a higher fold level. Add a syntax command :syntax foldlevel [start | minimum] to choose between these two methods of computing the foldlevel of a line.
* | | | vim-patch:8.2.1044: not all systemd file types are recognized (#12527)Jan Edmund Lazo2020-06-24
| | | | | | | | | | | | | | | | | | | | Problem: Not all systemd file types are recognized. Solution: Match several more files. (Guido Cella, closes vim/vim#6319) https://github.com/vim/vim/commit/ef6d86c173becdf82b7a9a1329342c9368340def
* | | | lsp: when apply text edits, set buflisted on buffers (#12489)francisco souza2020-06-23
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The client creates buffers on the fly to be able to apply text edits on files that weren't previously open, which is great, but it uses the bufadd() function, which creates unlisted buffers and can lead to a weird experience in the text editor. Setting the buffer to buflisted fixes this. Closes #12488. Co-authored-by: francisco souza <fsouza@users.noreply.github.com>
* | | vim-patch:8.2.0983: SConstruct file type not recognizedJan Edmund Lazo2020-06-18
| | | | | | | | | | | | | | | | | | Problem: SConstruct file type not recognized. Solution: Use python for SConstruct files. (Roland Hieber) https://github.com/vim/vim/commit/ad72350360d1a68d251da62a6e8610950926278c
* | | vim-patch:8.2.0980: raku file extension not recognizedJan Edmund Lazo2020-06-18
| | | | | | | | | | | | | | | | | | Problem: Raku file extension not recognized. (Steven Penny) Solution: Recognize .raku and .rakumod. (closes vim/vim#6255) https://github.com/vim/vim/commit/a65d8b5bb9e9267c6e4500c67d26c839a64f30eb
* | | vim-patch:8.2.0954: not all desktop files are recognizedJan Edmund Lazo2020-06-18
| | | | | | | | | | | | | | | | | | Problem: Not all desktop files are recognized. Solution: Add the *.directory pattern. (Eisuke Kawashima, closes vim/vim#3317) https://github.com/vim/vim/commit/f1f0ff9557353c9a452aac8540411a88cf2da47c
* | | vim-patch:8.1.1977: terminal debugger plugin may hangJan Edmund Lazo2020-06-18
| | | | | | | | | | | | | | | | | | Problem: Terminal debugger plugin may hang. Solution: Wait longer when still reading symbols. https://github.com/vim/vim/commit/19c8fe1925f4f7ffa1cc46e64d8bb8b1665ac437
* | | vim-patch:8.2.0930: script filetype detection trips over env -S argumentJan Edmund Lazo2020-06-18
| | | | | | | | | | | | | | | | | | | | | Problem: Script filetype detection trips over env -S argument. Solution: Remove "-S" and "--ignore-environment". (closes vim/vim#5013) Add tests. https://github.com/vim/vim/commit/b5e18f29fac9253b0ccf1fde5e74bff72fa1ba60
* | | vim-patch:8.2.0927: some sshconfig and ssdhconfig files are not recognizedJan Edmund Lazo2020-06-18
| | | | | | | | | | | | | | | | | | Problem: Some sshconfig and ssdhconfig files are not recognized. Solution: Add filetype patterns. https://github.com/vim/vim/commit/da84ac2a6f467d0b9eddcc8709433cda75d16a41
* | | vim-patch:8.0.1554: custom plugins loaded with --cleanJan Edmund Lazo2020-06-18
|/ / | | | | | | | | | | Problem: Custom plugins loaded with --clean. Solution: Do not include the home directory in 'runtimepath'. https://github.com/vim/vim/commit/072687032683b1994d25a114893d9a6f8bc36612
* | lsp: Add new highlight groups used in show_line_diagnostics (#12473)francisco souza2020-06-18
| | | | | | | | | | | | | | | | | | * lsp: support custom hl groups in show_line_diagnostics Closes #12472. * runtime: add docs for the new lsp highlight groups Co-authored-by: francisco souza <fsouza@users.noreply.github.com>
* | tex.vim: patch runtime/indent to 388a5d4f20b4Manuel Krebs2020-06-17
| | | | | | | | vim/vim@388a5d4f20b4b64341d1604aa238cab85827b892
* | tex.vim: patch runtime to 65e0d77a66b7Manuel Krebs2020-06-16
| | | | | | | | vim/vim@65e0d77a66b7
* | tex.vim: patch runtime to 388a5d4f20b4Manuel Krebs2020-06-16
| | | | | | | | vim/vim@388a5d4f20b4
* | tex.vim: patch runtime to 1d9215b9aaa1Manuel Krebs2020-06-16
| | | | | | | | vim/vim@1d9215b9aaa1
* | Merge pull request #12342 from h-michael/fix-docHirokazu Hata2020-06-15
|\ \
| * | doc: fix vim.api.nvim_buf_attach callback argumentsHirokazu Hata2020-06-15
| | |
* | | Merge pull request #12469 from h-michael/requestHirokazu Hata2020-06-15
|\ \ \ | | | | | | | | lsp: even if contents before change is 0 byte, request to server
| * | | lsp: even if contents before change is 0 byte, request to serverHirokazu Hata2020-06-11
| | | | | | | | | | | | | | | | fix: https://github.com/neovim/neovim/issues/12414
* | | | Fix highlight group names in LSP documentation (#12427)Kevin Fleming2020-06-14
| | | | | | | | | | | | | | | | | | | | | | | | LspDiagnosticInformation -> LspDiagnosticsInformation LspDiagnosticInformationSign -> LspDiagnosticsInformationSign LspDiagnosticHint -> LspDiagnosticsHint LspDiagnosticHintSign -> LspDiagnosticsHintSign
* | | | lsp: Fix text edits with the same start position (#12434)Andreas Johansson2020-06-14
| |_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | According to the LSP spec[1], multiple edits can have the same starting position, and if that is the case, they should be applied in the order as they come in the array. The implementation uses a reverse sort to not interfere with non applied edits, but failed to take into account the spec. [1] https://microsoft.github.io/language-server-protocol/specifications/specification-3-14/#textedit
* | | lsp: Add `BufLeave` to `close_preview_autocmd` function call (#12477)Dheepak Krishnamurthy2020-06-12
| | | | | | | | | else popup window remains open when switching buffer.
* | | lsp: Fix #12449 textDocumentSync.save can be boolean. Access ↵Stephan Seitz2020-06-11
|/ / | | | | | | textDocumentSync.save.includeText only if table. (#12450)
* | Add overlapped option to jobstarterw72020-06-10
| | | | | | | | | | | | | | When UV_OVERLAPPED_PIPE was used for the pipe passed to the child process, a problem occurred with the standard input of the .Net Framework application (#11809). Therefore, add the overlapped option to jobstart() and change it so that it is set only when necessary
* | Merge pull request #12321 from vigoux/treesitter-runtimeMatthieu Coudron2020-06-06
|\ \ | | | | | | treesitter: update runtime
| * | treesitter: fix testsThomas Vigouroux2020-06-03
| | |
* | | Merge pull request #12413 from janlazo/vim-8.2.0089Matthieu Coudron2020-06-06
|\ \ \ | | | | | | | | [RDY]vim-patch:8.0.1564,8.1.{917,1895,2018,2335},8.2.{89,491,873,892,905}
| * | | vim-patch:8.2.0491: cannot recognize a <script> mapping using maparg()Jan Edmund Lazo2020-06-04
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Cannot recognize a <script> mapping using maparg(). Solution: Add the "script" key. (closes vim/vim#5873) https://github.com/vim/vim/commit/2da0f0c445da3c9b35b2a0cd595d10e81ad2a6f9
| * | | vim-patch:8.2.0873: a .jl file can be sawfish (lisp) or JuliaJan Edmund Lazo2020-06-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: A .jl file can be sawfish (lisp) or Julia. Solution: Do not recognize *.jl as lisp, since it might be Julia. (closes vim/vim#6178) https://github.com/vim/vim/commit/2891459b81a21dbd2802ef1ae106c6680f085899
* | | | Merge pull request #12411 from kuuote/fix-remote-plugin-commandMatthieu Coudron2020-06-06
|\ \ \ \ | |/ / / |/| | | runtime: fix remote plugin command fails at some case
| * | | runtime: fix remote plugin command fails at some casekuuote2020-05-31
| | | | | | | | | | | | | | | | fixes #12410
* | | | lsp: do not process diagnostics for unloaded buffers (#12440)TJ DeVries2020-06-04
| | | |
* | | | lsp: compute height of floating preview correctly for wrapped lines (#12380)Christian Clason2020-06-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * take wrapping into account when computing float height * factor out size calculation * add test * accept and pass through opts.wrap_at in floating_preview * make padding configurable * slightly refactor fancy_floating_markdown to make use of make_position * padding using string.format * move trim and pad to separate function * nit Co-authored-by: Hirokazu Hata <h.hata.ai.t@gmail.com> * remove mention of backward compat * make lint happy Co-authored-by: Hirokazu Hata <h.hata.ai.t@gmail.com>
* | | | lsp: Add check for `declaration` and `typeDefinition` support in vim lsp ↵Dheepak Krishnamurthy2020-06-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | server before making `request` (#12421) * Add check for typeDefinition support in vim lsp server * Check for typeDefinitionProvider in server * Check for declarationProvider in server * Add check for client support * Fix typo
* | | | lua: fix behavior when split empty string (#12429)notomo2020-06-04
| | | | | | | | | | | | | | | | | | | | * lua: fix behavior when split empty string * test: lsp.util.apply_text_edits with an empty edit
* | | | Merge pull request #12343 from ndreas/fix/lsp-multibyte-indexingHirokazu Hata2020-06-04
|\ \ \ \ | | | | | | | | | | Fix LSP multibyte indexing
| * | | | Use get_line_byte_from_position in jump_to_locationAndreas Johansson2020-05-19
| | | | |
| * | | | Refactor fetching the line byteAndreas Johansson2020-05-19
| | | | | | | | | | | | | | | | | | | | Takes the entire LSP position instead of line/col
* | | | | Add v:event.visual during `TextYankPost` (#12382)Christian Clason2020-06-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * propagate visual selection to textyankpost event * adapt tests * add docs * also adapt oldtest
* | | | | lua: fix infinite loop for vim.split on empty string (#12420)notomo2020-06-02
| |_|/ / |/| | |
* | | | lua: add vim.highlight.range (#12401)Christian Clason2020-05-31
| |/ / |/| |
* | | vim-patch:8.2.0843: filetype elm not detected (#12403)Jan Edmund Lazo2020-05-30
| | | | | | | | | | | | | | | Problem: Filetype elm not detected. Solution: Recognize *.elm files. (closes vim/vim#6157) https://github.com/vim/vim/commit/0016fd2e29b7d4d4eef89a0516d14888a8651c61
* | | lua: vim.wait implementationTJ DeVries2020-05-30
| | |
generated by cgit (git 2.34.1) at 2025-06-25 05:58:08 +0000