aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* | | docs(support): update tested versions (#21126)dundargoc2022-11-20
| | |
* | | test: use isCI to simplify CI detection (#21134)dundargoc2022-11-20
|/ /
* | perf(diagnostic): use api variable and improve validate (#21111)Raphael2022-11-19
| | | | | | | | | | * fix(diagnostic): use api variable and improve validate * fix: fix test case
* | test: fix failing tui_spec.lua tests (#21117)Jakub Łuczyński2022-11-19
| | | | | | | | | | | | | | * refactor(test): use exec_lua * fix(test): fix failing tui_spec tests test is failing when path of tty-test does not fit cmdline
* | fix(lsp): ignore hover and signatureHelp responses on buffer change (#21121)Grzegorz Rozdzialik2022-11-19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Language servers can take some time to respond to the `textDocument/hover` and `textDocument/signatureHelp` messages. During that time, the user could have already moved to another buffer. The popup was always shown in the current buffer, which could be a different one than the buffer for which the request was sent. This was particularly annoying when moving to a buffer with a `BufLeave` autocmd, as that autocmd was triggered when the hover popup was shown for the original buffer. Ignoring the response from these 2 messages if they are for a buffer that is not the current one leads to less noise. The popup will only be shown for the buffer for which it was requested. A more robust solution could involve cancelling the hover/signatureHelp request if the buffer changes so the language server can free its resources. It could be implemented in the future.
* | vim-patch:partial:d13166e788fc (#21109)Sean Dewar2022-11-19
| | | | | | | | | | | | | | | | | | | | | | | | Update runtime files https://github.com/vim/vim/commit/d13166e788fcaef59ec65c20b46ca4be16625669 - Skip E1309-1311 (not ported). - Skip `:echowindow` changes (not ported). - Skip termdebug winbar doc changes (not fully ported). - Port missing `g:termdebug_config.{wide,use_prompt}` changes from v8.2.5010. Co-authored-by: Bram Moolenaar <Bram@vim.org>
* | feat(lsp): run handler in coroutine to support async response (#21026)Mathias Fußenegger2022-11-19
| | | | | | | | To illustrate a use-case this also changes `window/showMessageRequest` to use `vim.ui.select`
* | vim-patch:8.2.5130: edit test for mode message fails when using valgrind ↵zeertzjq2022-11-19
| | | | | | | | | | | | | | | | | | | | (#21118) Problem: Edit test for mode message fails when using valgrind. Solution: Use WaitForAssert(). Run beep test later. https://github.com/vim/vim/commit/c5382b667ac4b69ddff5b5bc562386843bc9c07b Co-authored-by: Bram Moolenaar <Bram@vim.org>
* | vim-patch:8.2.5148: invalid memory access when using expression on command ↵zeertzjq2022-11-19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | line (#21113) Problem: Invalid memory access when using an expression on the command line. Solution: Make sure the position does not go negative. https://github.com/vim/vim/commit/6046aded8da002b08d380db29de2ba0268b6616e N/A patches for version.c: vim-patch:8.2.5149: cannot build without the +eval feature Problem: Cannot build without the +eval feature. (Tony Mechelynck) Solution: Add #ifdefs. https://github.com/vim/vim/commit/6689df024bce4309ec5884e445738fe07ee4ffcc Co-authored-by: Bram Moolenaar <Bram@vim.org>
* | vim-patch:8.2.5167: get(Fn, 'name') on funcref returns special byte code ↵zeertzjq2022-11-19
| | | | | | | | | | | | | | | | | | | | | | | | (#21112) Problem: get(Fn, 'name') on funcref returns special byte code. Solution: Use the printable name. https://github.com/vim/vim/commit/1ae8c262df7083dfb4b41485508951c50eccc84c Cherry-pick printable_func_name() from patch 8.2.0149. Co-authored-by: Bram Moolenaar <Bram@vim.org>
* | vim-patch:8.2.0260: several lines of code are duplicated (#21108)zeertzjq2022-11-19
| | | | | | | | | | | | | | | | | | Problem: Several lines of code are duplicated. Solution: Move duplicated code to a function. (Yegappan Lakshmanan, closes vim/vim#5330) https://github.com/vim/vim/commit/f4140488c72cad4dbf5449dba099cfa7de7bbb22 Using sizeof seems better than ARRAY_SIZE for vim_snprintf().
* | feat(clipboard): added wayclip support (#21091)XDream82022-11-18
| |
* | Merge pull request #21104 from zeertzjq/vim-8.2.0469zeertzjq2022-11-18
|\ \ | | | | | | vim-patch:8.2.{0450,0469}
| * | vim-patch:8.2.0469: Vim9: no error for missing ] after listzeertzjq2022-11-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Vim9: no error for missing ] after list. Solution: Add error message. Add more tests. https://github.com/vim/vim/commit/ee619e5bc0992e818f2d9540b093b769b9c27651 Co-authored-by: Bram Moolenaar <Bram@vim.org>
| * | vim-patch:8.2.0450: not enough testing for restricted mode and function callszeertzjq2022-11-18
|/ / | | | | | | | | | | | | Problem: Not enough testing for restricted mode and function calls. Solution: Add more tests. (Yegappan Lakshmanan, closes vim/vim#5847) https://github.com/vim/vim/commit/7d941ee032c02a4b682201881eb5c1f1958f17ee
* | Merge pull request #21103 from zeertzjq/vim-8.2.4553zeertzjq2022-11-18
|\ \ | | | | | | vim-patch:8.2.{4553,4562}: linear tag search is not optimal
| * | vim-patch:8.2.4562: linear tag search is not optimalzeertzjq2022-11-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Linear tag search is not optimal. Solution: Improve linear tag search performance. (Yegappan Lakshmanan, closes vim/vim#9944) https://github.com/vim/vim/commit/b29b96806f1472371fb3cc01d48394e00b95cfc8 Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
| * | vim-patch:8.2.4553: linear tag search is a bit slowzeertzjq2022-11-18
|/ / | | | | | | | | | | | | | | | | Problem: Linear tag search is a bit slow. Solution: Remove a vim_ftell() call. (Yegappan Lakshmanan, closes vim/vim#9937) https://github.com/vim/vim/commit/8b530b3158cbd3aee2ad9cad8e7b7964faabb51e Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
* | Merge pull request #21102 from zeertzjq/vim-8.2.4512zeertzjq2022-11-18
|\ \ | | | | | | vim-patch:8.2.{4512,4518,4538,4543,4544}: find_tags_in_file() function is too long
| * | vim-patch:8.2.4544: Coverity warnings for not using returned valuezeertzjq2022-11-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Coverity warnings for not using returned value. Solution: Assign to vim_ignored. https://github.com/vim/vim/commit/dbf8094b17781ab1db191cf690e59c79f508a50f Co-authored-by: Bram Moolenaar <Bram@vim.org>
| * | vim-patch:8.2.4543: Coverity warning for refactored tag search codezeertzjq2022-11-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Coverity warning for refactored tag search code. Solution: Avoid the warnings. Update comments. Add one more test case. (Yegappan Lakshmanan, closes vim/vim#9928) https://github.com/vim/vim/commit/20fb28b1dcc092787e1a7b22dcfcfe1e46e29813 Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
| * | vim-patch:8.2.4538: the find_tags_in_file() function is too longzeertzjq2022-11-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: The find_tags_in_file() function is too long. Solution: Refactor into smaller functions. (Yegappan Lakshmanan, closes vim/vim#9920) https://github.com/vim/vim/commit/bf40e90dfeb1d3d0280077e65782beb3fee31c9f Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
| * | vim-patch:8.2.4518: the binary tag search feature is always enabledzeertzjq2022-11-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: The binary tag search feature is always enabled. Solution: Remove the #ifdefs. Add a few more tests. (Yegappan Lakshmanan, closes vim/vim#9893) https://github.com/vim/vim/commit/655b734ee858e90dd8d28549b7704a71b25d30e7 Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
| * | vim-patch:8.2.4512: the find_tags_in_file() function is much too longzeertzjq2022-11-18
|/ / | | | | | | | | | | | | | | | | | | | | | | Problem: The find_tags_in_file() function is much too long. Solution: Refactor into multiple smaller functions. (Yegappan Lakshmanan, closes vim/vim#9892) https://github.com/vim/vim/commit/df1bbea436636ac227d33dd79f77e07f4fffb028 Cherry-pick Test_tag_file_encoding() changes from patch 8.2.1432. Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
* | Merge pull request #21101 from zeertzjq/vim-8.2.4494zeertzjq2022-11-18
|\ \ | | | | | | vim-patch:8.2.{4494,4496}: find_tags() function is too long
| * | vim-patch:8.2.4496: Coverity gives warnings after tags code refactoringzeertzjq2022-11-18
| | | | | | | | | | | | | | | | | | | | | Problem: Coverity gives warnings after tags code refactoring. Solution: Avoid the warnings. (Yegappan Lakshmanan, closes vim/vim#9882) https://github.com/vim/vim/commit/fe9112e630672dcd95e6b384c86f50c27ec10fed
| * | vim-patch:8.2.4494: the find_tags() function is much too longzeertzjq2022-11-18
|/ / | | | | | | | | | | | | | | | | Problem: The find_tags() function is much too long. Solution: Refactor the function. (Yegappan Lakshmanan, closes vim/vim#9869) https://github.com/vim/vim/commit/2f87a99b6e9b559d51e130769e7f8377db6749f8 Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
* | vim-patch:8.2.3776: when a tags file line is long a tag may not be found ↵zeertzjq2022-11-18
| | | | | | | | | | | | | | | | | | | | (#21099) Problem: When a tags file line is long a tag may not be found. Solution: When increasing the buffer size read the same line again. https://github.com/vim/vim/commit/f8e9eb8e173bf0ff9560192ae888941ef8302269 Co-authored-by: Bram Moolenaar <Bram@vim.org>
* | feat(l10n): update zh_CN translations (#21085)Sizhe Zhao2022-11-18
| |
* | fix(ex_cmds): fix a mistake in the porting of Vim patch 8.1.0306 (#21096)zeertzjq2022-11-18
| |
* | vim-patch:9.0.0897: Clinical Quality Language files are not recognized (#21094)Matthew Gramigna2022-11-18
| | | | | | | | | | | | | | | | Problem: Clinical Quality Language files are not recognized. Solution: Add the "*.cql" pattern. (Matthew Gramigna, closes vim/vim#11452) https://github.com/vim/vim/commit/12babe45a389cd1ea8befd5b06239e877b4abbba Co-authored-by: mgramigna <mgramigna@mitre.org>
* | vim-patch:8.2.1497: CursorHold test is flaky (#21095)zeertzjq2022-11-18
| | | | | | | | | | | | | | | | Problem: CursorHold test is flaky. (Jakub Kądziołka) Solution: Use WaitForAssert() (closes vim/vim#6754) https://github.com/vim/vim/commit/17f67547f36a06220ea4667aaee7bb130108f568 Co-authored-by: Bram Moolenaar <Bram@vim.org>
* | Merge pull request #21078 from dundargoc/refactor/remove-wintbfredl2022-11-17
|\ \ | | | | | | refactor: remove __STDC_ISO_10646__ check
| * | refactor: remove __STDC_ISO_10646__ checkdundargoc2022-11-17
| | | | | | | | | | | | | | | We can always assume wchar_t values are unicode codepoints for the systems we support, so this check isn't necessary.
* | | Merge pull request #21090 from zeertzjq/vim-8.2.2945zeertzjq2022-11-17
|\ \ \ | | | | | | | | vim-patch:8.2.{2945,2952,2960,2973,2981,3080,3103,3440,3498},9.0.0895: recover tests
| * | | fix(memline): use long instead of linenr_T for db_line_countzeertzjq2022-11-17
| | | |
| * | | vim-patch:9.0.0895: file renamed twice in test, missing feature checkzeertzjq2022-11-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: File renamed twice in test; missing feature check. Solution: Remove a rename() call. Add check for cryptv feature. (closes vim/vim#11564) https://github.com/vim/vim/commit/780154bf7a07813e474105837c2b5998009d9c71 Co-authored-by: zeertzjq <zeertzjq@outlook.com>
| * | | vim-patch:8.2.3498: recover test may fail on some systemszeertzjq2022-11-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Recover test may fail on some systems. Solution: Adjust the little endian and 64 bit detection. (James McCoy, closes vim/vim#8941) https://github.com/vim/vim/commit/37f341d7236ff8a1e886bbb0f0ba0700ad589373 Co-authored-by: James McCoy <jamessan@jamessan.com>
| * | | vim-patch:8.2.3440: recover test fails if there is an old swap filezeertzjq2022-11-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Recover test fails if there is an old swap file. Solution: Delete old swap files. https://github.com/vim/vim/commit/f2a8bafa4b815e5b4e50a25c2b3a8a24fbe8aa11 Co-authored-by: Bram Moolenaar <Bram@vim.org>
| * | | vim-patch:8.2.3103: swap test may fail on some systemszeertzjq2022-11-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Swap test may fail on some systems when jobs take longer to exit. Solution: Use different file names. https://github.com/vim/vim/commit/f33cae605064c8bdb908a8069d936f752572cd76 Co-authored-by: Bram Moolenaar <Bram@vim.org>
| * | | vim-patch:8.2.3080: recover test fails on 32bit systemszeertzjq2022-11-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Recover test fails on 32bit systems. (Ondřej Súkup) Solution: Detect 32/64 bit systems. (Yegappan Lakshmanan, closes vim/vim#8485, closes vim/vim#8479) https://github.com/vim/vim/commit/576cb75ceb38ed077938d4a1c1265095050f6105 Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
| * | | vim-patch:8.2.2981: recovery test is not run on big-endian systemszeertzjq2022-11-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Recovery test is not run on big-endian systems. Solution: Make it work on big-endian systems. (James McCoy, closes vim/vim#8368) https://github.com/vim/vim/commit/6654ca702ca64c99965efcad3243ea5f95473252 Co-authored-by: James McCoy <jamessan@jamessan.com>
| * | | vim-patch:8.2.2973: fix for recovery and diff mode not testedzeertzjq2022-11-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Fix for recovery and diff mode not tested. Solution: Add a few more tests. (Yegappan Lakshmanan, closes vim/vim#8352) https://github.com/vim/vim/commit/3044324e8dccd470bd854cf7d9457232cc9c220e Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
| * | | vim-patch:8.2.2960: swap file recovery not sufficiently testedzeertzjq2022-11-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Swap file recovery not sufficiently tested. Solution: Add a few more tests. (Yegappan Lakshmanan, closes vim/vim#8339) https://github.com/vim/vim/commit/8cf02e5cf8fb14a5009f12e7af0a47617a0ce88d Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
| * | | vim-patch:8.2.2952: recover test fails on big endian systemszeertzjq2022-11-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Recover test fails on big endian systems. Solution: Disable the failing test on big endian systems. (Yegappan Lakshmanan, closes vim/vim#8335) https://github.com/vim/vim/commit/99285550a9957e2c8669f183557944c6513c4875 Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
| * | | vim-patch:8.2.2945: some buffer related code is not testedzeertzjq2022-11-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Some buffer related code is not tested. Solution: Add a few more tests. (Yegappan Lakshmanan, closes vim/vim#8320) https://github.com/vim/vim/commit/59b262362f26b3aaea1eeb0078adc33eed59863e Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
* | | | Merge pull request #20956 from gpanders/lua-readsecureGregory Anders2022-11-17
|\ \ \ \ | |/ / / |/| | | feat: implement vim.secure.read() and use it for 'exrc'
| * | | refactor: deprecate 'secure' optionGregory Anders2022-11-17
| | | | | | | | | | | | | | | | | | | | Now that 'exrc' files must be explicitly marked trusted there is no need to constrain what can be done in them.
| * | | feat(exrc): use vim.secure.read() for 'exrc' optionGregory Anders2022-11-17
| | | |
| * | | feat: add vim.secure.read()Gregory Anders2022-11-17
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | This function accepts a path to a file and prompts the user if the file is trusted. If the user confirms that the file is trusted, the contents of the file are returned. The user's decision is stored in a trust database at $XDG_STATE_HOME/nvim/trust. When this function is invoked with a path that is already marked as trusted in the trust database, the user is not prompted for a response.
generated by cgit (git 2.34.1) at 2025-07-08 01:41:36 +0000