aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* vim-patch:8.2.3096: temp files remain after running testszeertzjq2023-11-13
| | | | | | | | | Problem: Temp files remain after running tests. Solution: Delete the right files. (Dominique Pellé, closes vim/vim#8509) https://github.com/vim/vim/commit/6c72fd51a899e6f0c272b08b9784d3c7a3cede20 Co-authored-by: Dominique Pelle <dominique.pelle@gmail.com>
* vim-patch:8.2.3086: Vim9: breakpoint on "for" does not workzeertzjq2023-11-13
| | | | | | | | | Problem: Vim9: breakpoint on "for" does not work. Solution: Use the right line number in ISN_DEBUG. (closes vim/vim#8486) https://github.com/vim/vim/commit/6fc016168249360f0524b68f72cf33efd0574d40 Co-authored-by: Bram Moolenaar <Bram@vim.org>
* vim-patch:8.2.3066: Vim9: debugging lambda does not workzeertzjq2023-11-13
| | | | | | | | | | Problem: Vim9: debugging lambda does not work. Solution: Use the compile type of the function when compiling a lambda. (closes vim/vim#8412) https://github.com/vim/vim/commit/17d868b8b268c9b9670421039d1a772341937add Co-authored-by: Bram Moolenaar <Bram@vim.org>
* vim-patch:8.2.3039: Vim9: breakpoint at a comment line does not workzeertzjq2023-11-13
| | | | | | | | | | Problem: Vim9: breakpoint at a comment line does not work. Solution: Add the comment line number to the debug instruction. (closes vim/vim#8429) https://github.com/vim/vim/commit/8cec9273d2518f2a9abcbd326722a2eba38d2a13 Co-authored-by: Bram Moolenaar <Bram@vim.org>
* vim-patch:8.2.3027: Vim9: breakpoint in compiled function not always checkedzeertzjq2023-11-13
| | | | | | | | | | Problem: Vim9: breakpoint in compiled function not always checked. Solution: Check for breakpoint when calling compiled function from compiled function. https://github.com/vim/vim/commit/2ac4b2536a40e5cd75b4ff7a3d44a282d2f4f008 Co-authored-by: Bram Moolenaar <Bram@vim.org>
* vim-patch:8.2.3026: Vim9: cannot set breakpoint in compiled functionzeertzjq2023-11-13
| | | | | | | | | Problem: Vim9: cannot set breakpoint in compiled function. Solution: Check for breakpoint when calling a function. https://github.com/vim/vim/commit/4f8f54280fa728b7d5a63b67d02b60a3b3dce543 Co-authored-by: Bram Moolenaar <Bram@vim.org>
* vim-patch:8.2.3017: Vim9: debugger shows too many lineszeertzjq2023-11-13
| | | | | | | | | Problem: Vim9: debugger shows too many lines. Solution: Truncate at a comment, "enddef", etc. (closes vim/vim#8392) https://github.com/vim/vim/commit/59b50c3bee908694ae4ac10b26bfebf99d09d466 Co-authored-by: Bram Moolenaar <Bram@vim.org>
* vim-patch:8.2.3013: Vim: when debugging only first line of command is displayedzeertzjq2023-11-13
| | | | | | | | | | | Problem: Vim: when debugging only the first line of a command using line continuation is displayed. Solution: Find the next command and concatenate lines until that one. (closes vim/vim#8392) https://github.com/vim/vim/commit/4cea536bdf48df459e7ad651dfee006844bbf2c0 Co-authored-by: Bram Moolenaar <Bram@vim.org>
* vim-patch:8.2.3011: Vim9: cannot get argument values during debuggingzeertzjq2023-11-13
| | | | | | | | | | Problem: Vim9: cannot get argument values during debugging. Solution: Lookup names in the list of arguments. Put debug instruction halfway for command. https://github.com/vim/vim/commit/6bc30b05e6081bcaece6d1a7fcfca238ea5a194f Co-authored-by: Bram Moolenaar <Bram@vim.org>
* vim-patch:8.2.3003: Vim9: closure compiled with wrong compile typezeertzjq2023-11-13
| | | | | | | | | Problem: Vim9: closure compiled with wrong compile type. Solution: Use COMPILE_TYPE() when calling a function. (closes vim/vim#8384) https://github.com/vim/vim/commit/968a5b62ffd3e08005d907d93eaaf807be466a88 Co-authored-by: Bram Moolenaar <Bram@vim.org>
* vim-patch:8.2.2996: Vim9: when debugging cannot inspect local variableszeertzjq2023-11-13
| | | | | | | | | Problem: Vim9: when debugging cannot inspect local variables. Solution: Make local variables available when debugging. https://github.com/vim/vim/commit/b69c6fb7b423ddc4578b093cb19257cad459dfae Co-authored-by: Bram Moolenaar <Bram@vim.org>
* vim-patch:8.2.2985: Vim9: a compiled function cannot be debuggedzeertzjq2023-11-13
| | | | | | | | | Problem: Vim9: a compiled function cannot be debugged. Solution: Add initial debugging support. https://github.com/vim/vim/commit/e99d422bbd3e47620915bf89671673f0711671b4 Co-authored-by: Bram Moolenaar <Bram@vim.org>
* build: enforce PREFER_LUAdundargoc2023-11-12
| | | | | Only search for luajit if PREFER_LUA=OFF. If PREFER_LUA is OFF, then always prioritize luajit first and then fall back to lua.
* vim-patch:9.0.2103: recursive callback may cause issues on some archs (#26013)zeertzjq2023-11-13
| | | | | | | | | | | | | | | | | | | | | | | Problem: recursive callback may cause issues on some archs Solution: Decrease the limit drastically to 20 Recursive callback limit causes problems on some architectures Since commit 47510f3d6598a1218958c03ed11337a43b73f48d we have a test that causes a recursive popup callback function to be executed. However it seems the current limit of 'maxfuncdepth' option value is still too recursive for some 32bit architectures (e.g. 32bit ARM). So instead of allowing a default limit of 100 (default value for 'maxfuncdepth'), let's reduce this limit to 20. I don't think there is a use case where one would need such a high recursive callback limit and a limit of 20 seems reasonable (although it is currently hard-coded). closes: vim/vim#13495 closes: vim/vim#13502 https://github.com/vim/vim/commit/2076463e383901cef44685aaf4b63e4306444f9e Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:2dd613f57bf1 (#26009)zeertzjq2023-11-13
| | | | | | | | | | runtime(termdebug): improve the breakpoint sign label (vim/vim#13525) // related vim/vim#12589 // that should be the last chat (I) with Bram, r.i.p https://github.com/vim/vim/commit/2dd613f57bf17eb8ff050bcb5510eb0279f5c9ab Co-authored-by: Shane-XB-Qian <shane.qian@foxmail.com>
* refactor: replace manual header guards with #pragma oncedundargoc2023-11-12
| | | | | It is less error-prone than manually defining header guards. Pretty much all compilers support it even if it's not part of the C standard.
* build: remove PVSdundargoc2023-11-12
| | | | | | | We already have an extensive suite of static analysis tools we use, which causes a fair bit of redundancy as we get duplicate warnings. PVS is also prone to give false warnings which creates a lot of work to identify and disable.
* build: use stylua with add_glob_targetdundargoc2023-11-12
| | | | | | | stylua version 0.19.0 has added the flag `--respect-ignores` which unbreaks stylua when used with add_glob_target. See eecddd24164c3c4a250aec25dbd760b283849981 for more context.
* feat(lsp)!: vim.lsp.inlay_hint.get(), enable(), is_enabled() #25512LW2023-11-12
| | | | | | | | | | | | | | | | | | refactor!: `vim.lsp.inlay_hint()` -> `vim.lsp.inlay_hint.enable()` Problem: The LSP specification allows inlay hints to include tooltips, clickable label parts, and code actions; but Neovim provides no API to query for these. Solution: Add minimal viable extension point from which plugins can query for inlay hints in a range, in order to build functionality on top of. Possible Next Steps --- - Add `virt_text_idx` field to `vim.fn.getmousepos()` return value, for usage in mappings of `<LeftMouse>`, `<C-LeftMouse>`, etc
* vim-patch:9.0.2101: CI: test_termdebug may still fail (#26003)zeertzjq2023-11-12
| | | | | | | | | | Problem: CI: test_termdebug may still fail Solution: use term_wait() to make it more robust closes: vim/vim#13529 https://github.com/vim/vim/commit/fdbadea4b60e5e1a0bf192dc5ee04d8ab06f4399 Co-authored-by: shane.xb.qian <shane.qian@foxmail.com>
* vim-patch:2c133f6c1a16Christian Clason2023-11-12
| | | | | | | | runtime(lynx): Update for Lynx 2.8.9 (vim/vim#13510) https://github.com/vim/vim/commit/2c133f6c1a165a74678a89722ed8c42967c295e4 Co-authored-by: dkearns <dougkearns@gmail.com>
* fix(float): apply 'winblend' to title/footer highlight (#25999)zeertzjq2023-11-12
|
* vim-patch:9358b8d99349 (#25998)zeertzjq2023-11-12
| | | | | | | | | | runtime(vim): Improve :let-heredoc syntax highlighting (vim/vim#12923) "trim" and "eval" are allowed in any order and whitespace is not required after "=<<". https://github.com/vim/vim/commit/9358b8d99349818666718f513655c2bf53d43754 Co-authored-by: dkearns <dougkearns@gmail.com>
* vim-patch:9.0.2100: CI: test_termdebug fails (#25997)zeertzjq2023-11-12
| | | | | | | | | | | | Problem: CI: test_termdebug fails Solution: only test for a changed winlayout, if the window width actually changed Also, include an unrelated comment (which doesn't warrant its own patch number) https://github.com/vim/vim/commit/305127f9f2f6058b4ec071041a2c98f76114a9b0 Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:9.0.2098: No filetype support for xcompose files (#25983)ObserverOfTime2023-11-12
| | | | | | | | Problem: No filetype support for xcompose files Solution: Add filetype detection closes: vim/vim#13508 https://github.com/vim/vim/commit/4f9074b96cc7efb1c829ca74902a851551dcf4e8
* vim-patch:1b08d2cd0789 (#25993)zeertzjq2023-11-12
| | | | | | | | | runtime(doc): clarify when formatoptions applies closes: vim/vim#13503 https://github.com/vim/vim/commit/1b08d2cd0789fd9aaae148a64ff46342730022d7 Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:9.0.2097: No support for cypher filesChristian Clason2023-11-12
| | | | | | | | | | | | | | | | Problem: No support for cypher files Solution: Add cypher filetype detection Cypher query language support to work with (mostly) graph databases. Already existing lsp support in Neovim's nvim-lspconfig: https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#cypher_ls closes: vim/vim#13516 https://github.com/vim/vim/commit/8f0fe20ff1a13b468fdfaf85c434475f75c7a615 Co-authored-by: Gerrit Meier <meistermeier@gmail.com>
* fix(PVS/V564): the '|' operator is applied to bool type valuedundargoc2023-11-11
|
* fix(PVS/V1001): variable is assigned but is not useddundargoc2023-11-11
|
* vim-patch:5994329667a6Christian Clason2023-11-11
| | | | | | | | | runtime(i3config): Update for i3 4.23 (vim/vim#13522) https://github.com/vim/vim/commit/5994329667a630b85fae07b9121668456e86b22d Co-authored-by: Ivan Grimaldi <grimaldi.ivan@gmail.com> Co-authored-by: Ivan Grimaldi <grimaldi.ivam@gmail.com>
* ci: skip api-doc workflow on draft PRsdundargoc2023-11-11
| | | | | Checking the documentation generation is mostly useful towards the end of a pull request like with the lintcommit workflow.
* refactor: remove redundant castsdundargoc2023-11-11
|
* fix(PVS/V009): add top-level messagedundargoc2023-11-11
|
* fix(highlight): apply 'winblend' to float border (#25981)zeertzjq2023-11-11
|
* fix(context): don't leak memory on multiple invalid objects (#25979)zeertzjq2023-11-11
|
* fix(context): don't crash on invalid arg to nvim_get_context (#25977)zeertzjq2023-11-11
| | | | Note: The crash happens in the second test case when using uninitialized memory, and therefore doesn't happen with ASAN.
* fix(completion): make sure the buffer name is valid (#25975)mortezadadgar2023-11-11
| | | | | | | | | | | | Problem: crash from set complete+=f open a empty buffer C-N Solution: make sure the buffer name is valid. regression from ae4ca4edf89ece433b61e8bf92c412298b58d9ea
* test: skip failing test on freebsddundargoc2023-11-10
| | | | | The watch_file test started failing on bsd after 3ca967387c49c754561c3b11a574797504d40f38.
* docs: update contributingdundargoc2023-11-10
|
* PVS fixesdundargoc2023-11-10
| | | | | | | | | | | | | * build(PVS): exclude mpack and klib as they are external dependencies * build(PVS): suppress warning V601 See https://pvs-studio.com/en/docs/warnings/v601/ * fix(PVS/V009): add top-level message * fix(PVS/V547): expression 'p != NULL' is always true * fix(PVS/V547): expression '* termpp == NULL' is always false
* build(deps): bump tree-sitter-markdown to v0.1.7Christian Clason2023-11-10
|
* build(deps): bump luajit to HEAD - 69bbbf773Christian Clason2023-11-10
|
* Merge pull request #25954 from bfredl/noxmallocbfredl2023-11-10
|\ | | | | refactor(drawline): avoid xmalloc/xfree cycles on each screenline
| * refactor(drawline): avoid xmalloc/xfree cycles on each screenlinebfredl2023-11-09
| |
* | ci: remove UBSAN_OPTIONS environment variable (#25963)zeertzjq2023-11-10
| | | | | | | | | | Because it overrides log_path from ASAN_OPTIONS. Ref https://github.com/google/sanitizers/issues/1675
* | fix(f_wait): flush UI before blocking (#25962)zeertzjq2023-11-10
| |
* | vim-patch:8.2.4078: terminal test for current directory not used on FreeBSD ↵zeertzjq2023-11-10
| | | | | | | | | | | | | | | | | | | | | | (#25961) Problem: Terminal test for current directory not used on FreeBSD. Solution: Make it work on FreeBSD. (Ozaki Kiichi, closes vim/vim#9516) Add TermWait() inside Run_shell_in_terminal() as a generic solution. https://github.com/vim/vim/commit/ced2b38a560cc4f4ec983ed2cf4372ab62e1dbc1 Co-authored-by: Bram Moolenaar <Bram@vim.org>
* | fix(options): do not change inccommand during preview (#25462)Omar El Halabi2023-11-09
| |
* | refactor: change some xstrndup() and xstrnsave() to xmemdupz() (#25959)zeertzjq2023-11-10
| | | | | | | | When the given length is exactly the number of bytes to copy, xmemdupz() makes the intention clearer.
* | vim-patch:d56f15caf602Christian Clason2023-11-09
| | | | | | | | | | | | | | | | runtime(wget): Update for Wget2 2.1.0 (vim/vim#13497) https://github.com/vim/vim/commit/d56f15caf602a061f5f9f0a3c6a4537ab2dc6acc Co-authored-by: dkearns <dougkearns@gmail.com>
generated by cgit (git 2.34.1) at 2025-06-24 12:03:08 +0000