aboutsummaryrefslogtreecommitdiff
path: root/runtime
Commit message (Collapse)AuthorAge
* feat: aggregate code actions from all clients (#15121)Folke Lemaitre2021-07-18
|
* doc(lsp): various small fixes (#15113)Ido Ariel2021-07-17
| | | | | | - remove incorrect usage of docstrings - fix make_formatting_params return type documentation to 'DocumentFormattingParams' - make progress_handler private - fix links
* Merge pull request #15017 from donbex/local-file-uriMichael Lingelbach2021-07-14
|\ | | | | fix(lsp): accept file URIs without a hostname
| * feat(vim.uri): Allow URI schemes other than file: without authorityTom Payne2021-07-10
| |
| * fix(lsp): accept file URIs without a hostnameAlessandro Pezzoni2021-07-10
| | | | | | | | | | | | | | RFC 8089, which defines the file URI scheme, also allows URIs without a hostname, i.e. of the form file:/path/to/file. These are returned by some language servers and accepted by other LSP implementations, such as VSCode's, so it is reasonable for us to accept them as well.
* | fix(lsp): pass bufnr for async formatting (#15084)Michael Lingelbach2021-07-14
| | | | | | | | | | | | the `textDocument/rangeFormatting` nad `textDocument/formatting` did not pass bufnr to apply_text_edits, meaning edits were applied to the user's currently active buffer. This could result in text being applied to the wrong buffer.
* | feat(job): add parameter to close stdinGregory Anders2021-07-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some programs behave differently when they detect that stdin is being piped. This can be problematic when these programs are used with the job control API where stdin is attached, but not typically used. It is possible to run the job using a PTY which circumvents this problem, but that includes a lot of overhead when simply closing the stdin pipe would suffice. To enable this behavior, add a new parameter to the jobstart options dict called "stdin" with two valid values: "pipe" (the default) implements the existing behavior of opening a channel for stdin and "null" which disconnects stdin (or, if you prefer, connects it to /dev/null). This is extensible so that other modes can be added in the future.
* | fix(lsp): avoid ipairs on non-sequential tables (#15059)Michael Lingelbach2021-07-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ipairs terminates on the first nil index when iterating over table keys: for i,k in ipairs( {[1] = 'test', [3] = 'test'} ) do print(i, k) end prints: 1 test Instead, use pairs which continues iterating over the entire table: for i,k in pairs( {[1] = 'test', [3] = 'test'} ) do print(i, k) end prints: 1 test 3 test
* | fixup(clipboard): Fix error not properly handled #14984Shadman2021-07-11
| | | | | | fixes #14967
* | fix(lsp): Ensure human readable errors are printedMathias Fussenegger2021-07-11
| | | | | | | | | | | | | | | | | | | | `return err_message(tostring(err))` caused errors to be printed as `table: 0x123456789` instead of showing the error code and error message. This also removes some `if err` blocks that never got called because at the end of `handlers.lua` all the handlers are wrapped with logic that adds generic error handling.
* | fix(lsp): Ensure users get feedback on references/symbols errors or empty ↵Mathias Fussenegger2021-07-11
| | | | | | | | | | | | | | | | | | results Relates to https://github.com/neovim/neovim/issues/15050 Users should get some indication if there was an error or an empty result.
* | fix(lsp): Add separator between codelens in virttext (#15049)Mathias Fußenegger2021-07-10
| | | | | | | | | | | | | | | | | | | | | | | | Before: Lens1Lens2 After: Lens1 | Lens2 Fixes https://github.com/neovim/neovim/issues/15048
* | fix(lsp): correctly check for windows in lsp logger (#14954)Oliver Marriott2021-07-10
| |
* | feat(lsp): Make line diagnostics display prettierMathias Fussenegger2021-07-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds indentation that matches the number prefix to ensure diagnostic messages spawning multiple lines align. Before: Diagnostics: 1. • Variable not in scope: red :: t0 -> t • Perhaps you meant one of these: ‘rem’ (imported from Prelude), ‘read’ (imported from Prelude), ‘pred’ (imported from Prelude) 2. • Variable not in scope: repeDoubleColon :: [Char] -> t0 • Perhaps you meant ‘replaceDoubleColon’ (line 32) After: Diagnostics: 1. • Variable not in scope: red :: t0 -> t • Perhaps you meant one of these: ‘rem’ (imported from Prelude), ‘read’ (imported from Prelude), ‘pred’ (imported from Prelude) 2. • Variable not in scope: repeDoubleColon :: [Char] -> t0 • Perhaps you meant ‘replaceDoubleColon’ (line 32)
* | docs: regeneratemarvim2021-07-09
| |
* | fix(lsp): support duplicate params in signature help (#15032)Folke Lemaitre2021-07-09
| |
* | docs: regeneratemarvim2021-07-08
| |
* | fix(lsp): restore diagnostics extmarks that were moved to the last edit line ↵Folke Lemaitre2021-07-08
| | | | | | | | (#15023)
* | feat(lsp): highlight active parameter in signature help (#15018)Folke Lemaitre2021-07-07
| |
* | doc: "--remote" is not supported #14936cbarrete2021-07-07
| | | | | | | | There are plans to support the --remote-xx stuff (or something like it): #1750 #8326 But we don't need this doc meanwhile.
* | doc: remove mentions of compile-time flags #14935cbarrete2021-07-07
|/ | | | Nvim always compiles everything in so those are useless at best and confusing at worst.
* fix(lsp): restore diagnostics extmarks on buffer changes (#15011)Folke Lemaitre2021-07-07
|
* fix(lsp): prevent double <text> for cached plaintext markupFolke Lemaitre2021-07-05
|
* Merge pull request #14981 from janlazo/vim-8.2.3081Jan Edmund Lazo2021-07-04
|\ | | | | vim-patch:8.2.{3081,3082,3085,3087,3088,3093,3094,3097,3098}
| * vim-patch:8.2.3087: Gemtext files are not recognizedJan Edmund Lazo2021-07-04
| | | | | | | | | | | | Problem: Gemtext files are not recognized. Solution: Recognize .gmi and .gemini files. (closes vim/vim#8427) https://github.com/vim/vim/commit/fcde67c99fbb6d7294e01b9e87d8d2ae7af31255
| * vim-patch:8.2.3085: JSONC files are not recognizedJan Edmund Lazo2021-07-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: JSONC files are not recognized. Solution: Recognize .jsonc files. (Izhak Jakov, closes vim/vim#8500) https://github.com/vim/vim/commit/acbb4b5720fc27b8b07357b763ed4e5a944ae1da N/A patches for version.c: vim-patch:8.2.3081: cannot catch errors in a channel command Problem: Cannot catch errors in a channel command. Solution: Instead of skipping the error make it silent. (closes vim/vim#8477) https://github.com/vim/vim/commit/11a632d60bde616feb298d180108819ebb1d04a0 vim-patch:8.2.3082: a channel command "echoerr" does not show anything Problem: A channel command "echoerr" does not show anything. Solution: Do not use silent errors when using an "echoerr" command. (closes vim/vim#8494) https://github.com/vim/vim/commit/b836f631dba2534efd314a8f77439cebc75acd4e vim-patch:8.2.3094: Test_popup_atcursor_pos() fails without the conceal feature Problem: Test_popup_atcursor_pos() fails without the conceal feature. Solution: Add a check for the conceal feature. (Dominique Pellé, closes vim/vim#8505) https://github.com/vim/vim/commit/c60e959cba03fae9cff9b2674fab646cc70819fc vim-patch:8.2.3098: popup window test is flaky on MS-Windows with GUI Problem: Popup window test is flaky on MS-Windows with GUI. Solution: Skip the check in this situation. https://github.com/vim/vim/commit/999db2346b61e6f6e6fde2d0b56f4646a46b727d
* | fix(vim.opt): vimL map string values not trimmed (#14982)jadedpasta2021-07-04
|/ | | | | | | | | Options formatted as a list of comma-separated key-value pairs may have values that contain leading and trailing whitespace characters. For example, the `listchars` option has a default value of `"tab:> ,trail:-,nbsp:+"`. When converting this value to a lua table, leading and trailing whitespace should not be trimmed. Co-authored-by: Robert Hrusecky <robert.hrusecky@utexas.edu>
* doc/startup: cleanup; assign ENN to "conflicing configs" msg (#14971)Justin M. Keyes2021-07-03
|
* fixup(clipboard): Use case matching #14962Shadman2021-07-02
| | | Context: https://github.com/neovim/neovim/pull/14848#discussion_r663203173
* version bumpBjörn Linse2021-07-02
|
* doc(options): Fix recommended PowerShell config (#14349)Dimitri Tcaciuc2021-07-02
| | | | | | | | | | | Ensure that * Shell uses UTF8 input/output mode * Stderr output is captured, in UTF8 * Program exit codes are correctly captured Update functional test harness and add tests for :make command. Closes #13713
* runtime/vim: d2ea7cf10a4d026ebd402594d656af7d5c811c24 (#14950)Christian Clason2021-07-01
| | | Port vim syntax file only.
* BugFix(clipboard): Fix block paste not working properlyshadmansaleh2021-07-01
| | | | | | | | | | | Block copy and paste from system-clipboard currently breaks formatting. This fixes it. The bug occurs because system-clipboard doesn't contain information about what mode the copy was made. Simple solution to this is we keep a cache of copy we last made along with mode information. If system-clipboard returns the cache we apply the mode information that we know about that cache.
* fix(vim.opt): Fix #14828 with empty values being incorrectly insertedTJ DeVries2021-06-29
|
* fix(vim.opt): Fix #14668 Now correctly handles unescaped commas in isfname styleTJ DeVries2021-06-29
|
* fix(vim.opt): Fix #14669 whichwrap now acts as expectedTJ DeVries2021-06-29
|
* fix(vim.opt): Add basic error handlingDavid Zhang2021-06-29
|
* fix(vim.opt): Get window options before setting.ckipp012021-06-29
| | | | | | | This closes #14677, but I also am a little unsure if there are times where this may not be correct. However, this just changes the behavior that even if `was_set` was false, we still get for `nvim_win_get_option`.
* fix(vim.opt): #14708 Now lets you put duplicate values in wildmodeTJ DeVries2021-06-29
|
* fix(doc/api): Remove 'border' as unsupported (#14916)Daniel Steinberg2021-06-28
| | | PR #13998 added support for floating window borders.
* fix(doc): remove reference to vim.lsp.callbacks (#14576)Matthieu Coudron2021-06-28
| | | | too old now, can be confusing
* [RDY] Add buffer information to tabline_update (#12481)John Gehrig2021-06-27
| | | | | | | | | | * Add buffer information to tabline_update Most terminal implementations of the tabline display buffer and tab information. Many neovim-qt users disable GuiTabline because it lacks functionality provided in the terminal implementation. The tabline_update event should include buffer information too, so client GUIs can display rich useful tabs.
* Fixed +1 -1 in util.lua (#14913)jimman20032021-06-26
| | | No point in adding and then subtracting I believe ;)
* vim-patch:8.2.2954: short file name extension for Scala not recognizedJan Edmund Lazo2021-06-26
| | | | | | Problem: Short file name extension for Scala not recognized. Solution: Recognize *.sc. (closes vim/vim#8337) https://github.com/vim/vim/commit/6db7b6375a3ea3afef5295b1366896902012e640
* vim-patch:8.2.3049: JSON patch file not recognizedJan Edmund Lazo2021-06-26
| | | | | | Problem: JSON patch file not recognized. Solution: Recognize json-patch as json. (Kevin Locke, closes vim/vim#8450) https://github.com/vim/vim/commit/6582e230a0f6592287b1123c5fc3807d6fed997e
* vim-patch:8.2.3050: cannot recognize elixir filesJan Edmund Lazo2021-06-26
| | | | | | | Problem: Cannot recognize elixir files. Solution: Recognize Elixir-specific files. Check if an .ex file is Euphoria or Elixir. (Austin Gatlin, closes vim/vim#8401, closes vim/vim#8446) https://github.com/vim/vim/commit/f3caeb63d62c08b579e9b5f40b35e8bf64dde87a
* fix(doc/usr_41): don't mention 0o prefix for octs (#14906)Sean Dewar2021-06-25
| | | | | | v8.2.0886 isn't ported yet. Also remove mentions of Vim9 and legacy script for now. [skip ci]
* fix(lsp): render the last line in stylize_markdownFolke Lemaitre2021-06-25
|
* Merge pull request #14910 from folke/lsp_fences_docsMichael Lingelbach2021-06-25
|\ | | | | style(lsp): make get_markdown_fences private
| * style(lsp): make get_markdown_fences privateFolke Lemaitre2021-06-25
| |