aboutsummaryrefslogtreecommitdiff
path: root/test
Commit message (Collapse)AuthorAge
* Added testBK16032020-07-02
|
* terminal: preserve mode when using <Cmd>wincmd in terminal mode (#12254)Ghjuvan Lacambre2020-06-22
|
* Merge pull request #12455 from janlazo/vim-8.0.1554Matthieu Coudron2020-06-22
|\ | | | | [RDY]vim-patch:8.0.1554,8.1.1977,8.2.{927,930,932,938,954,963,964,966,980,983,998,999}
| * vim-patch:8.2.0966: 'shortmess' flag "n" not used in two placesJan Edmund Lazo2020-06-18
| | | | | | | | | | | | | | Problem: 'shortmess' flag "n" not used in two places. Solution: Make use of the "n" flag consistent. (Nick Jensen, closes vim/vim#6245, closes vim/vim#6244) https://github.com/vim/vim/commit/722e505d1a55dfde5ab62241d10da91d2e10c3c1
| * 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
* | eval: fix assertion failure in garbage collection (#12436)erw72020-06-22
|/ | | | | | | | | | | | | | | | | | | | | | | * eval: fix assertion failure in garbage collection fixes #12387, #12430 Lists with CopyID+1 linked only from previous_funccal may be removed in the garbage collection. Therefore, the terms of the assertions are not correct. This can be confirmed by the following (The l:x with CopyID+1 of the first function call needs to be removed by garbage collection): func! s:f() let l:x = [1] let g:x = l: endfunc for _ in range(2) call s:f() endfor call garbagecollect() " press any key * test: add test for #12387, #12430
* 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>
* 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
* test: Fix ignored LSP tests (#12470)David Lukes2020-06-11
| | | | | | | | | * Fix ignored LSP tests * Restructure _make_floating_popup_size tests Co-authored-by: Christian Clason <christian.clason@uni-due.de> Co-authored-by: Christian Clason <christian.clason@uni-due.de>
* Merge pull request #12376 from erw7/fix-stack-overflow-on-input-enqueueMatthieu Coudron2020-06-08
|\ | | | | input: fix stack overflow
| * nvim_input: add testerw72020-05-25
| |
* | vim-patch:8.2.0111: VAR_SPECIAL is also used for booleansBilly Su2020-06-06
| | | | | | | | | | | | Problem: VAR_SPECIAL is also used for booleans. Solution: Add VAR_BOOL for better type checking. https://github.com/vim/vim/commit/9b4a15d5dba354d2e1e02871470bad103f34769a
* | Merge pull request #12321 from vigoux/treesitter-runtimeMatthieu Coudron2020-06-06
|\ \ | | | | | | treesitter: update runtime
| * | treesitter: fix testsThomas Vigouroux2020-06-03
| | |
| * | treesitter: update runtimeThomas Vigouroux2020-06-02
| | | | | | | | | | | | | | | Since tree-sitter PR 615, predicates are not parsed the same. "Old" way of writing predicates is still supported.
* | | Merge pull request #12416 from teto/openbsd_fixMatthieu Coudron2020-06-06
|\ \ \ | | | | | | | | ci: bump openbsd image
| * | | test: remove flaky unhelpful testTJ DeVries2020-06-06
| | | | | | | | | | | | | | | | vim.wait( sthg)
* | | | 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
* | | | Merge pull request #12411 from kuuote/fix-remote-plugin-commandMatthieu Coudron2020-06-06
|\ \ \ \ | |/ / / |/| | | runtime: fix remote plugin command fails at some case
| * | | test: rewrite to multiple argumentskuuote2020-06-01
| | | |
| * | | runtime: fix remote plugin command fails at some casekuuote2020-05-31
| |/ / | | | | | | | | | fixes #12410
* | | 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>
* | | 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
| * | | Add tests for jump_to_locationAndreas Johansson2020-05-19
| | | |
* | | | 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: vim.wait implementationTJ DeVries2020-05-30
| | |
* | | API: nvim_create_buf: unset 'modeline' in scratch-buffer #12379Justin M. Keyes2020-05-29
| | | | | | | | | | | | Although 'nomodeline' is not strictly part of the definition of a "scratch-buffer" it is obviously the right default.
* | | lua: simple snippet support in the completion items (#12118)Viktor Kojouharov2020-05-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Old behavior is: foo(${placeholder: bar, ...) with lots of random garbage you'd never want inserted. New behavior is: foo(bar, baz) (which maybe is good, maybe is bad [depends on user], but definitely better than it was). ----- * Implement rudimentary snippet parsing Add support for parsing and discarding snippet tokens from the completion items. Fixes #11982 * Enable snippet support * Functional tests for snippet parsing Add simplified real-world snippet text examples to the completion items test * Add a test for nested snippet tokens * Remove TODO comment * Return the unmodified item if the format is plain text * Add a plain text completion item
* | | lsp: make the command error message more detailed (#11633)Hirokazu Hata2020-05-26
| | | | | | | | | | | | | | | * lsp.lua: make the error message more detailed * test: add lsp._cmd_part test
* | | Merge pull request #10905 from erw7/vim-8.1.0475Matthieu Coudron2020-05-25
|\ \ \ | |_|/ |/| | vim-patch:8.1.{475,800,868,1007,1027,1031,1033,1037,1058,1435,1484,1485}
| * | vim-patch:8.1.1435: memory usage test is a bit too flakyerw72020-05-07
| | | | | | | | | | | | | | | | | | Problem: Memory usage test is a bit too flaky. Solution: Adjust the tolerances a bit. (Christian Brabandt) https://github.com/vim/vim/commit/5d508dd39e810d446f29dfd4f4e745b802875001
| * | vim-patch:8.1.1058: memory usage test may still fail on some systemserw72020-05-07
| | | | | | | | | | | | | | | | | | Problem: Memory usage test may still fail on some systems. Solution: Use 98% of the lower limit. (Christian Brabandt) https://github.com/vim/vim/commit/3a731ee0c2dd34792c1b21fc4c699a84129f1b86
| * | vim-patch:8.1.1037: memory usage test may still fail on some systemserw72020-05-07
| | | | | | | | | | | | | | | | | | Problem: Memory usage test may still fail on some systems. Solution: Increase tolerance from 3% to 20%. https://github.com/vim/vim/commit/6b6f7aae4a3329d685e512699287605540257b40
| * | vim-patch:8.1.1033: memory usage test may still fail on some systemserw72020-05-07
| | | | | | | | | | | | | | | | | | | | | Problem: Memory usage test may still fail on some systems. (Elimar Riesebieter) Solution: Increase tolerance from 1% to 3%. https://github.com/vim/vim/commit/ba64ba093520e85d6bed2595960edb693bdb4c51
| * | vim-patch:8.1.1031: memory usage test may still failerw72020-05-07
| | | | | | | | | | | | | | | | | | Problem: Memory usage test may still fail. Solution: Drop the unused min value. (Christian Brabandt) https://github.com/vim/vim/commit/f7e47af7760fe054cb645dac9a1e96b23c85804d
| * | vim-patch:8.1.1027: memory usage test sometimes failserw72020-05-07
| | | | | | | | | | | | | | | | | | Problem: Memory usage test sometimes fails. Solution: Use 80% of before.last as the lower limit. (Christian Brabandt) https://github.com/vim/vim/commit/08cda65ddfbb4bce8cef43726a0c00817fc47327
| * | vim-patch:8.1.1007: using closure may consume a lot of memoryerw72020-05-07
| | | | | | | | | | | | | | | | | | | | | Problem: Using closure may consume a lot of memory. Solution: unreference items that are no longer needed. Add a test. (Ozaki Kiichi, closes vim/vim#3961) https://github.com/vim/vim/commit/209b8e3e3bf7a4a3d102134124120f6c7f57d560
* | | vim-patch:8.1.2233: cannot get the Vim command line arguments (#12117)kuuote2020-05-24
| | | | | | | | | | | | | | | Problem: Cannot get the Vim command line arguments. Solution: Add v:argv. (Dmitri Vereshchagin, closes vim/vim#1322) https://github.com/vim/vim/commit/69bf634858a2a75f2984e42b1e4017bc529a040a
* | | Change uri_to_fname to not convert non-file URIs (#12351)Mathias Fußenegger2020-05-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | * Change uri_to_fname to not convert non-file URIs A URI with a scheme other than file doesn't have a local file path. * fixup! Change uri_to_fname to not convert non-file URIs * fixup! fixup! Change uri_to_fname to not convert non-file URIs
* | | fixed hang issue with --headless and -r option specified (#12209)Kei Kamikawa2020-05-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * fixed hang issue with --headless and -r option specified Calling the do_more_prompt function in headless mode will freeze neovim because it is eventally in the input-accepting state (the same as waiting for --more--). * fixed "Press ENTER or type command to continue" to be suppressed If in headless mode, we need to exit at this point. If we continue, we will enter the normal mode and the message "Press ENTER or type command to continue" will be displayed and we will be in the input waiting state. * fixed functional ex_cmds tests * Revert "fixed "Press ENTER or type command to continue" to be suppressed" This reverts commit a02dc40e3b3fad69cedcde6abe1bd4efe39ab102. * Revert "fixed functional ex_cmds tests" This reverts commit 3bdb8da20acf34673b2c2028d15e7ce6da4c792a. * fixed conditional again * added test for fixed hang issue with --headless (#11386)
* | | test: fix flaky vim.defer_fn testHirokazu Hata2020-05-19
| | |
* | | lua: Add highlight.on_yank (#12279)Christian Clason2020-05-18
| |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * add lua function to highlight yanked region * extract namespace, better naming, default values * add default for event argument * free timer * factor out mark to position calculation * d'oh * make sure timer stops before callback (cf. luv example) * factor out timer, more documentation * fixup * validate function argument for schedule * fix block selection past eol * correct handling of multibyte characters * move arguments around, some cleanup * move utility functions to vim.lua * use anonymous namespaces, avoid local api * rename function * add test for schedule_fn * fix indent * turn hl-yank into proper (hightlight) module * factor out position-to-region function mark extraction now part of highlight.on_yank * rename schedule_fn to defer_fn * add test for vim.region * todo: handle double-width characters * remove debug printout * do not shadow arguments * defer also callable table * whitespace change * move highlight to vim/highlight.lua * add documentation * add @return documentation * test: add check before vim.defer fires * doc: fixup
* | lsp: Handle end lines in apply_text_edits (#12314)Andreas Johansson2020-05-17
| | | | | | | | | | | | If the LSP sends an end line that is larger than what nvim considers to be the last line, you get an Index out of bounds error when fetching the line from nvim, a change that was introduced in #12223. This change removes the strict indexing and checks the return value from nvim_buf_get_lines.
* | lua: add tbl_deep_extend (#11969)Hirokazu Hata2020-05-17
| |
* | lsp: fix bug when documentEdit version=null for unattached buffer (#12272)landerlo2020-05-13
| |
* | LSP: Make applyEdit return a response (#12270)Mathias Fußenegger2020-05-11
| | | | | | | | | | | | | | | | According to the specification workspace/applyEdit needs to respond with a `ApplyWorkspaceEditResponse` See https://microsoft.github.io/language-server-protocol/specifications/specification-current/#workspace_applyEdit This is a subset of https://github.com/neovim/neovim/pull/11607
* | Merge #12275 from erw7/profile-fix-use-after-freeJustin M. Keyes2020-05-09
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | viml/profile: fix missing fixes when merging vim-patch:8.1.0130 Fix #12255 ### Steps to reproduce using `nvim -u NORC` ``` nvim -u NORC :function Test() :endfunction :profile start log1 :profile func Test :call Test() :profile stop :profile start log2 :profile func Test :call Test() :profile stop ``` ### Actual behaviour #### log1 ``` FUNCTION Test() Called 1 times ... ``` #### log2 ``` FUNCTION Test() Called 2 times ... ``` ### Expected behaviour #### log1 ``` FUNCTION Test() Called 1 times ... ``` #### log2 ``` FUNCTION Test() Called 1 times ... ```