aboutsummaryrefslogtreecommitdiff
path: root/runtime
Commit message (Collapse)AuthorAge
* Merge pull request #13229 from ElPiloto/more_treesitter_docThomas Vigouroux2020-11-05
|\ | | | | [RDY] doc: Supplement documentation for treesitter.
| * Update runtime/doc/treesitter.txtLuis Piloto2020-11-05
| | | | | | Co-authored-by: Thomas Vigouroux <tomvig38@gmail.com>
| * doc: Fix treesitter doc PR.ElPiloto2020-11-04
| |
| * doc: Supplement documentation for treesitter.ElPiloto2020-11-04
| | | | | | | | | | | | | | | | - Describe query components (capture, match, pattern). Not well-described in tree-sitter documentation. - Describe Query() object. Not actually described anywhere in documenation.
* | Add g:loaded_matchit check (#13226)Shougo2020-11-04
| | | | | | I have added g:loaded_matchit check to skip matchit loading like other default plugins.
* | healthcheck: suggest to skip tests perl provider (#13223)Jan Edmund Lazo2020-11-04
|/ | | | CPAN tests are unreliable on Windows. CI does the same to reduce flaky,slow builds.
* treesitter: separate tree and parserThomas Vigouroux2020-11-04
| | | | While this might sound silly, it is needed for further improvements.
* docs: Fix typo in example codeLucas Hoffmann2020-11-03
|
* Merge pull request #13178 from steelsojka/fix-empty-main-query-fileThomas Vigouroux2020-11-02
|\ | | | | fix(treesitter): account for no main query file
| * fix(treesitter): account for no main query fileSteven Sojka2020-10-28
| |
* | lsp: remove vim.NIL from processing (#13174)TJ DeVries2020-11-02
| | | | | | | | | | * lsp: remove vim.NIL from processing * lsp: remove instances of vim.NIL
* | vim-patch:8.2.0864: pragmas are indented all the way to the leftJan Edmund Lazo2020-11-01
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Pragmas are indented all the way to the left. Solution: Add an option to indent progmas like normal code. (Max Rumpf, closes vim/vim#5468) https://github.com/vim/vim/commit/d881b516da0184052d2f9d33c3f72c5c014316bd N/A patches for version.c: vim-patch:8.1.2030: tests fail when build with normal features and terminal Problem: Tests fail when build with normal features and terminal. (Dominique Pelle) Solution: Disable tests that won't work. (closes vim/vim#4932) https://github.com/vim/vim/commit/997d42427eaab889058eb047e08d55de9e4a968a vim-patch:8.1.2063: some tests fail when +balloon_eval_term is missing Problem: Some tests fail when +balloon_eval_term is missing but _balloon_eval is present. (Dominique Pelle) Solution: Check the right feature in the test. (closes vim/vim#4962) https://github.com/vim/vim/commit/1e82a784ace6d2c4dce594dd6156bcb0028bba9e vim-patch:8.2.1938: wiping out a terminal buffer makes some tests fail Problem: Wiping out a terminal buffer makes some tests fail. Solution: Do not wipe out the terminal buffer unless wanted. https://github.com/vim/vim/commit/a46765a79745ff27b4a44659fb8389519c961977
* | lsp: complete support for `CodeActionKind`s to capabilities (#13180)Jesse2020-11-01
| | | | | | | | | | We support applying all kinds in the spec equivalently and some servers (including dartls) won't send code actions if support for the relevant kinds is not explicitly stated in the client capabilities. Therefore, this PR makes that support explicit. Also, as we support all CodeActionKinds, we should also mark the server as supporting code actions when it specifies code action kinds. This is also done in this PR.
* | Merge pull request #13192 from bfredl/nodeidBjörn Linse2020-11-01
|\ \ | | | | | | ] treesitter: add node:id()
| * | treesitter: add node:id()Björn Linse2020-11-01
| | |
* | | Merge pull request #13167 from romgrk/vim-8.2.1909Jan Edmund Lazo2020-10-31
|\ \ \ | | | | | | | | vim-patch:8.2.1909: number of status line items is limited to 80
| * | | vim-patch:8.2.1909: number of status line items is limited to 80Rom Grk2020-10-31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Number of status line items is limited to 80. Solution: Dynamically allocate the arrays. (Rom Grk, closes vim/vim#7181) https://github.com/vim/vim/commit/8133cc6bf454eb90bb0868f7cf806fce5c0c9fe6 The members of stl_item_T have not been prefixed with stl_ contrary to the vim patch because the amount of stl_ prefixes on single lines of code in that region was hurtful to readability.
* | | | lsp: Remove snippet lies (#13183)TJ DeVries2020-10-30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We don't actually support snippets in core in the way that users would truly expect. So, by default, we will not say that builtin-lsp has `snippetSupport`. To re-enable, users can do the following: First, get a capabilities dictionary with `local capabilities = vim.lsp.protocol.make_client_capabilities()` Then override `capabilities.textDocument.completion.completionItem.snippetSupport = true` and then pass those capabilties to the setup function. ``` nvim_lsp.server_name.setup { ..., capabilities = capabilities, ..., } ``` See https://github.com/neovim/neovim/issues/12795
* | | | Merge pull request #13172 from janlazo/vim-8.2.1910Jan Edmund Lazo2020-10-30
|\ \ \ \ | |_|/ / |/| | | vim-patch:8.1.{2034,2050},8.2.{131,913,929,1521,1910,1913,1922}
| * | | vim-patch:8.1.2034: dark them of GTK 3 not supportedJan Edmund Lazo2020-10-29
| | |/ | |/| | | | | | | | | | | | | Problem: Dark them of GTK 3 not supported. Solution: Add the "d" flag in 'guioptions'. (Jonathan Conder, closes vim/vim#4934) https://github.com/vim/vim/commit/50bf7ce0c9f8c3ede2d1a02c734beba9d5a0504e
* / | Fix clipboard provider detection (#13190)necabo2020-10-29
|/ / | | | | Fixes #13189
* / lsp: Fix case where active_signature == vim.NIL (#13114)Michael Lingelbach2020-10-27
|/
* vim-patch:8.1.1769: 'shellslash' is also used for completionskippi2020-10-26
| | | | | | Problem: 'shellslash' is also used for completion. Solution: Add the 'completeslash' option. (Yasuhiro Matsumoto, closes vim/vim#3612) https://github.com/vim/vim/commit/ac3150d385e6e3f3fe76642aac3cda954d30583f
* Merge pull request #13154 from fsouza/fix-callback-logicMatthieu Coudron2020-10-25
|\ | | | | [RDY] lsp: fix fallback for callback in method_unsupported
| * lsp: fix fallback for callback in method_unsupportedfrancisco souza2020-10-25
| | | | | | | | Missed this #12764. My bad :((
* | lsp: Store diagnostics for unloaded buffers (#13102)Mathias Fußenegger2020-10-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | To avoid loading buffers https://github.com/neovim/neovim/pull/12440 changed the logic to not process diagnostics for unloaded buffers. This is problematic for language servers where compile errors or build errors are reported via diagnostics. These errors may prevent the language server from providing all functions and it is difficult for users to debug it without having access to the errors. For example, with eclipse.jdt.ls there may be a problem with gradle (the build tool for java), it results in a diagnostics like this: org.gradle.toolingapi/build.gradle|1 col 1| Could not run build action using Gradle distribution 'https://services.gradle.org/distributions/gradle-4.8.1-bin.zip'. This would be invisible to users unless the user happens to open the right file. In this case the user would actually never see the error, because the language server isn't attached to the build configuration files. This changes the behaviour to at least store the diagnostics. The other operations which are more expensive are still skipped.
* | Merge pull request #13077 from tjdevries/tjdevries/buf_apis_1Björn Linse2020-10-25
|\ \ | |/ |/| api: nvim_buf_delete
| * api: nvim_buf_deleteTJ DeVries2020-10-22
| |
* | lsp: only send buf requests to servers that support the request (#12764)francisco souza2020-10-25
| | | | | | | | | | | | | | | | | | | | | | | | | | Refactors how required capabilities are detected and validated, and make sure requests are only sent to clients that support it (and only fail if no clients support the provided method). The validation happens at the buf_request level, because we assume that if someone is sending the request directly through the client, they know what they're doing. Also, let unknown methods go through. This is extracted from #12518 and closes #12755. Co-authored-by: francisco souza <fsouza@users.noreply.github.com>
* | Merge pull request #13132 from willelz/markdownJan Edmund Lazo2020-10-23
|\ \ | | | | | | runtime: Patch syntax/markdown.vim
| * | markdown.vim: patch runtime to ade0d3946801willelz2020-10-22
| | | | | | | | | | | | vim/vim@ade0d39468014fd55d30f7647a1ac104baff4bc5
| * | markdown.vim: patch runtime/ftplugin to c08ee7476b19willelz2020-10-22
| | | | | | | | | | | | vim/vim@c08ee7476b19f9b4de5df287797af87c4e3fba0a
* | | vim-patch:8.2.0901: formatting CJK text isn't optimalJan Edmund Lazo2020-10-23
| | | | | | | | | | | | | | | | | | Problem: Formatting CJK text isn't optimal. Solution: Properly break CJK lines. (closes vim/vim#3875) https://github.com/vim/vim/commit/e52702f00322c8a8861efd0bd6a3775e685e5685
* | | vim-patch:8.2.0952: no simple way to interrupt VimJan Edmund Lazo2020-10-22
| |/ |/| | | | | | | | | | | Problem: No simple way to interrupt Vim. Solution: Add the SigUSR1 autocommand, triggered by SIGUSR1. (Jacob Hayes, closes vim/vim#1718) https://github.com/vim/vim/commit/be5ee8686a50acf07b823bd293f9c765e533d213
* | lsp: Fix "client has shut down" errors during initializing (#13103)Mathias Fußenegger2020-10-22
|/ | | | | | | | | | Language servers can already send log messages to the client while the server is still being initialized. This currently leads to "client has shut down" messages which are confusing to the user as the server is properly starting. To fix this this changes the `get_client_by_id` method to also return a client if it is still initializing.
* vim-patch:8.2.1874: can't do something just before leaving Insert modeJan Edmund Lazo2020-10-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Can't do something just before leaving Insert mode. Solution: Add the InsertLeavePre autocommand event. (closes vim/vim#7177) https://github.com/vim/vim/commit/b53e13a91ab2fc9d52bd044715daa84972f4ce47 N/A patches for version.c: vim-patch:8.1.1877: graduated features scattered Problem: Graduated features scattered. Solution: Put graduated and obsolete features together. https://github.com/vim/vim/commit/ffc0716af8e448ef8a2a3249edfd0260546933df vim-patch:8.2.1875: warning when building GTK gui Problem: Warning when building GTK gui. Solution: Add missing function parameter. https://github.com/vim/vim/commit/3da855c8e28140d9f02b1572e445f8d4f977cf64 vim-patch:8.2.1877: test for function list fails Problem: Test for function list fails. Solution: Move "obsolete" comments one line up. https://github.com/vim/vim/commit/b8f519e5382f9876ae7f8bc64d9814d07a8ef972 vim-patch:8.2.1878: GTK: error for redefining function Problem: GTK: error for redefining function. (Tony Mechelynck) Solution: Remove "gtk_" prefix from local functions and prepend "gui_" to global functions. https://github.com/vim/vim/commit/8a99e66b4f7616d9b0b9cefe742f82f9122087d5 vim-patch:8.2.1881: cannot build with GTK3 Problem: Cannot build with GTK3. Solution: Adjust form functions. https://github.com/vim/vim/commit/692d1a51e74fea2db3c7e9ae7c7c6c3a1a1945ee vim-patch:8.2.1883: compiler warnings when using Python Problem: Compiler warnings when using Python. Solution: Adjust PyCFunction to also have the second argument. Use "int" return type for some functions. Insert "(void *)" to get rid of the remaining warnings. https://github.com/vim/vim/commit/4ce5fe4c87820c7d22964d6e91d7b07e96640e6f
* vim-patch:8.1.1056: no eval function for RubyAlex Genco2020-10-21
| | | | | | Problem: No eval function for Ruby. Solution: Add rubyeval(). (Ozaki Kiichi, closes vim/vim#4152) https://github.com/vim/vim/commit/e99be0e6d28fad96efd2b2be23fa38e7559e80e1
* Revert "vim-patch:8.1.1015: quickfix buffer shows up in list, can't get ↵Jan Edmund Lazo2020-10-20
| | | | | | buffer number" This reverts commit 4cd69151cf39cd4c3f083da2275f17206dcf5bc3.
* docs: update apiBjörn Linse2020-10-20
|
* Merge pull request #13043 from tkuneck/fix-min-float-win-sizeJan Edmund Lazo2020-10-17
|\ | | | | [RDY] Opts.wrap_at is sometimes a bool, ensure it falls back to a valid num…
| * Opts.wrap_at is sometimes a bool, ensure it falls back to a valid number in ↵Tony Kuneck2020-10-04
| | | | | | | | the call to math.min
* | Merge pull request #12053 from tjdevries/tjdevries/nicer_validateTJ DeVries2020-10-17
|\ \ | | | | | | vim.validate(): include stacktrace in message
| * | test/vim.validate(): assert normalized stacktraceJustin M. Keyes2020-10-05
| | | | | | | | | | | | | | | | | | | | | - The previous commit lost information in the tests. Instead, add some more "normalization" substitutions in pcall_err(), so that the general shape of the stacktrace is included in the asserted text. - Eliminate contains(), it is redundant with matches()
| * | vim.validate(): include stacktrace in messageTJ DeVries2020-10-05
| | |
* | | vim-patch:8.2.0868: trim() always trims both endsskippi2020-10-17
| | | | | | | | | | | | | | | | | | | | | Problem: trim() always trims both ends. Solution: Add an argument to only trim the beginning or end. (Yegappan Lakshmanan, closes vim/vim#6126) https://github.com/vim/vim/commit/2245ae18e3480057f98fc0e5d9f18091f32a5de0
* | | vim-patch:8.1.0221: not enough testing for the Ruby interfaceJan Edmund Lazo2020-10-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Not enough testing for the Ruby interface. Solution: Add more tests. (Dominique Pelle, closes vim/vim#3252) https://github.com/vim/vim/commit/edd6aacb010ad2402fc98f19e7f6b7c29ba2656f Modified some tests to make them pass for Neovim. Some tests will always fail because +ruby is externalized in Neovim. Skip failing ruby tests for now.
* | | treesitter: allow multiple highlighters per bufferThomas Vigouroux2020-10-12
| | |
* | | treesitter: allow custom parser for highlighterThomas Vigouroux2020-10-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Also allow to get parser ranges. This will be useful for language injection, allowing us to tweak the parser's ranges on the fly. Update runtime/lua/vim/treesitter.lua Co-authored-by: Paul Burlumi <paul@burlumi.com>
* | | Merge pull request #13059 from vigoux/ts-runtime-queriesBjörn Linse2020-10-12
|\ \ \ | | | | | | | | treesitter: runtime queries
| * | | treesitter: runtime queriesThomas Vigouroux2020-10-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Runtime queries just work like ftplugins, that is: - Queries in the `after` directory are sourced _after_ the "base" query - Otherwise, the last define query takes precedence. Queries can be found in the `queries` directory. Update runtime/lua/vim/treesitter/query.lua Co-authored-by: Paul Burlumi <paul@burlumi.com>
generated by cgit (git 2.34.1) at 2025-06-25 17:06:49 +0000