aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* | build(deps): bump luajit to HEAD - 8af63f992Christian Clason2023-09-12
| |
* | build(deps): bump tree-sitter to HEAD - 46af27796Christian Clason2023-09-12
| |
* | vim-patch:62145db91b10Christian Clason2023-09-12
| | | | | | | | | | | | | | | | syntax(i3config): improved i3config highlighting (vim/vim#13054) https://github.com/vim/vim/commit/62145db91b104075277cb3a940e18832ad106264 Co-authored-by: Josef Litoš <54900518+JosefLitos@users.noreply.github.com>
* | vim-patch:f787ee8451a1 (#25103)zeertzjq2023-09-12
| | | | | | | | | | | | | | | | | | runtime(doc): Add g:c_syntax_for_h to filetype-overrule docs closes: vim/vim#13074 https://github.com/vim/vim/commit/f787ee8451a1f24de4ef3de48b78d5aa77d09829 Co-authored-by: Doug Kearns <dougkearns@gmail.com>
* | vim-patch:596ad66d1ddb (#25102)zeertzjq2023-09-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | runtime(doc): documentation updates This is a collection of various improvements to the help pages closes vim/vim#12790 https://github.com/vim/vim/commit/596ad66d1ddb742ef349e98eb06b8e4052f68f51 Co-authored-by: Christian Brabandt <cb@256bit.org> Co-authored-by: Houl <anwoku@yahoo.de> Co-authored-by: Doug Kearns <dougkearns@gmail.com> Co-authored-by: Adri Verhoef <a3@a3.xs4all.nl>
* | fix(decorations): better approximation of botline #24794Jaehwang Jung2023-09-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: * The guessed botline might be smaller than the actual botline e.g. when there are folds and the user is typing in insert mode. This may result in incorrect treesitter highlights for injections. * botline can be larger than the last line number of the buffer, which results in errors when placing extmarks. Solution: * Take a more conservative approximation. I am not sure if it is sufficient to guarantee correctness, but it seems to be good enough for the case mentioned above. * Clamp it to the last line number. Co-authored-by: Lewis Russell <me@lewisr.dev>
* | fix(tests): set SHELL=sh #24941Sergey Slipchenko2023-09-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Some tests fail with $SHELL=fish #6172 Related: https://github.com/neovim/neovim/pull/6176 Solution: Replace "echo -n" with "printf", because "echo" in sh may be provided as a shell builtin, which does not accept an "-n" flag to avoid a trailing newline (e.g. on macos). "printf" is more portable (defined by POSIX) and it does not output a trailing newline by itself. Fixes #6172 TODO: Other test failures may be related to "session leader" issue: https://github.com/neovim/neovim/issues/2354 Checked by running `:terminal ./build/bin/tty-test` from Nvim with `shell=/bin/fish` (inherited from `$SHELL`) and it indeed complains about "process does not own the terminal". With `shell=sh` it doesn't complain. And unsetting `$SHELL` seems to make `nvim` to fall back to `shell=sh`. FAILED test/functional/terminal/tui_spec.lua @ 1017: TUI paste: terminal mode test/functional/terminal/tui_spec.lua:1024: Row 1 did not match. Expected: |*tty ready | |*{1: } | |* | | | |{5:^^^^^^^ }| |{3:-- TERMINAL --} | |{3:-- TERMINAL --} | Actual: |*process does not own the terminal | |* | |*[Process exited 2]{1: } | | | |{5:^^^^^^^ }| |{3:-- TERMINAL --} | |{3:-- TERMINAL --} | To print the expect() call that would assert the current screen state, use screen:snapshot_util(). In case of non-deterministic failures, use screen:redraw_debug() to show all intermediate screen states. stack traceback: test/functional/ui/screen.lua:622: in function '_wait' test/functional/ui/screen.lua:352: in function 'expect' test/functional/terminal/tui_spec.lua:1024: in function <test/functional/terminal/tui_spec.lua:1017> FAILED test/functional/terminal/tui_spec.lua @ 1551: TUI forwards :term palette colors with termguicolors test/functional/terminal/tui_spec.lua:1567: Row 1 did not match. Expected: |*{1:t}ty ready | | | |* | | | |{2:^^^^^^^ }| | | |{3:-- TERMINAL --} | Actual: |*{1:p}rocess does not own the terminal | | | |*[Process exited 2] | | | |{2:^^^^^^^ }| | | |{3:-- TERMINAL --} | To print the expect() call that would assert the current screen state, use screen:snapshot_util(). In case of non-deterministic failures, use screen:redraw_debug() to show all intermediate screen states. stack traceback: test/functional/ui/screen.lua:622: in function '_wait' test/functional/ui/screen.lua:352: in function 'expect' test/functional/terminal/tui_spec.lua:1567: in function <test/functional/terminal/tui_spec.lua:1551>
* | refactor(usercmd.c): reduce scope of localsLewis Russell2023-09-11
| |
* | Merge pull request #25083 from bfredl/memlinetypebfredl2023-09-11
|\ \ | | | | | | refactor(memline): cleanup typedefs for memline structs
| * | refactor(memline): cleanup typedefs for memline structsbfredl2023-09-10
| | | | | | | | | | | | | | | These were used interchangedly by the struct name and the typedef name. Use standard pattern type names and use these consistently
* | | Merge pull request #24901 from faergeek/more-intuitive-cursor-updatebfredl2023-09-11
|\ \ \ | | | | | | | | fix(api): more intuitive cursor updates in nvim_buf_set_text
| * | | fix(api): more intuitive cursor updates in nvim_buf_set_textSergey Slipchenko2023-09-11
| | | | | | | | | | | | | | | | Fixes #22526
* | | | vim-patch:9.0.1891: No runtime support for MojoChristian Clason2023-09-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: No runtime support for Mojo Solution: Add basic filetype and syntax plugins closes: vim/vim#13062 closes: vim/vim#13063 https://github.com/vim/vim/commit/0ce2c594d0704f27a16d2c13fce85d596cc91489 Co-authored-by: Mahmoud Abduljawad <mahmoud@masaar.com>
* | | | vim-patch:e7833e73471aChristian Clason2023-09-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | runtime(masm): add support for AVX-2 and AVX-512 (vim/vim#13061) https://github.com/vim/vim/commit/e7833e73471a110c7c38c80935e1b840f254a3da Co-authored-by: Wu Yongwei <wuyongwei@gmail.com>
* | | | vim-patch:066103307534Christian Clason2023-09-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | runtime(scala): Fix Scala highlighting string literal as type param (vim/vim#13070) Since https://docs.scala-lang.org/sips/42.type.html which is implemented in Scala 2.13 and in Scala 3 it possible to use string literals as singleton types. So code like ``` someFunc["abc"] ``` is valid. Currently this code is not hightlighted correctly and worse if there is an unclosed `(` in the string it breaks the formating in the rest of the file. I also submitted this patch to the mentioned project for this runtime file: https://github.com/derekwyatt/vim-scala/pull/173 But there are no commits there over the last 2 years and no response in the week since I created it. Also the last change to the Scala syntax file: https://github.com/vim/vim/pull/9594 is yet to be backported to that repo. Therefore I am opening this PR as well to get some feedback on how to proceed to get this fixed. https://github.com/vim/vim/commit/066103307534f81de08a092aac3a15e864a5a25f Co-authored-by: Emil Ejbyfeldt <eejbyfeldt@liveintent.com>
* | | | ci(cirrus): use FreeBSD 13.2 (#24684)zeertzjq2023-09-11
| | | |
* | | | Merge pull request #25093 from zeertzjq/vim-9.0.1893zeertzjq2023-09-11
|\ \ \ \ | |/ / / |/| | | vim-patch:9.0.{1893,1894}
| * | | vim-patch:9.0.1894: CI: trailing whitespace in testszeertzjq2023-09-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: CI: trailing white space in tests Solution: clean up the trailing white space https://github.com/vim/vim/commit/e5f7cd0a60d0eeab84f7aeb35c13d3af7e50072e Co-authored-by: Christian Brabandt <cb@256bit.org>
| * | | vim-patch:9.0.1893: CI: strptime test fails on BSD14zeertzjq2023-09-11
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | Problem: CI: strptime test fails on BSD14 Solution: Skip the test https://github.com/vim/vim/commit/983d808674f998eaea12b302028de45f1c6857cd Co-authored-by: Christian Brabandt <cb@256bit.org>
* | | fix(mouse): click on 'statuscolumn' with 'rightleft' (#25090)zeertzjq2023-09-11
| | |
* | | test: unignore test which froze sourcehut (#25067)Sergey Slipchenko2023-09-11
|/ /
* | Merge pull request #24875 from bfredl/memfilemapbfredl2023-09-10
|\ \ | | | | | | refactor(memfile): change mf_trans and mf_hash from ad-hoc hashtable to Map
| * | refactor(mch): last mch_ function/macro hits the dustbfredl2023-09-10
| | | | | | | | | | | | Also remove some stray comments.
| * | refactor(memfile): change mf_trans and mf_hash from ad-hoc hashtable to Mapbfredl2023-09-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Memfile used a private implementation of an open hash table with intrusive collision chains, but there is no reason to assume the standard khash_t based Map won't work just fine. Yes, we are taking full ownership and maintenance over memline and memfile. No one is going to maintain it for us. Trust the plan.
* | | ci(codeql): add concurrency to cancel unnecessary jobs earlydundargoc2023-09-10
| | |
* | | ci: install stylua from their releasesdundargoc2023-09-10
| | | | | | | | | | | | It's quicker to grab the .zip file rather than using homebrew.
* | | build: remove luarocksdundargoc2023-09-10
|/ / | | | | | | | | Luarocks is no longer needed after 25e51d393a420765d5efd44c1b4be823a5cf280a.
* | build(deps): bump luajit to HEAD - 5a18d4582Christian Clason2023-09-10
| |
* | Merge pull request #25071 from bfredl/coxpcallbfredl2023-09-10
|\ \ | | | | | | build(lua): vendor coxpcall
| * | build(lua): vendor coxpcallbfredl2023-09-10
| | | | | | | | | | | | Do not require luarocks on PUC lua CI just because of this single lua file
* | | vim-patch:733bbcde776eChristian Clason2023-09-10
| | | | | | | | | | | | | | | | | | | | | | | | runtime(nasm): updated syntax file https://github.com/vim/vim/commit/733bbcde776e857b45bf4c713a3c9203ac728040 Co-authored-by: Andrii Sokolov <andriy145@gmail.com>
* | | feat(lsp): improve control over placement of floating windows (#24494)Grace Petryk2023-09-10
| | |
* | | fix: fix compiler warning from clangdundargoc2023-09-09
|/ /
* | fix(deps): make sure --force-config takes effectSergey Slipchenko2023-09-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes #24881 --force-config passed to luarocks' configure script is only taken into account in case "make install" is used afterwards. But if "make bootstrap" is used then this flag has no effect. And it can actually copy an existing config on the system to the new installation. That existing config can have a different version of Lua set by default. In which case luarocks will install packages for that version instead of the one used in tests. And trying to run tests then will fail because of missing packages.
* | revert: "ci: trigger tests when pushing"dundargoc2023-09-09
| | | | | | | | | | | | | | | | | | This reverts commit e71c7898ca3cf3af1243227ff3cba526d48897e8. Triggering jobs on users own fork turned out to be not that useful, and only necessary in rare moments. It's easier to adjust the CI scripts if the users wants CI results before creating a pull request. It also reduces the complexity of the CI code.
* | ci(release): remove unnecessary full clonedundargoc2023-09-09
| |
* | fix(rpc): fix hang with channel closed while waiting for responseSergey Slipchenko2023-09-09
| |
* | Merge pull request #25039 from glepnir/fix_hlbfredl2023-09-09
|\ \ | | | | | | fix(highlight): add create param in nvim_get_hl api function
| * | fix(highlight): add create param in nvim_get_hlglepnir2023-09-09
| |/
* | Merge pull request #25058 from zeertzjq/vim-9.0.1886zeertzjq2023-09-09
|\ \ | | | | | | vim-patch:9.0.{1877,partial:1886}
| * | vim-patch:partial:9.0.1886: Various Typoszeertzjq2023-09-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Various Typos Solution: Fix Typos This is a collection of typo related commits. closes: vim/vim#12753 closes: vim/vim#13016 https://github.com/vim/vim/commit/ee17b6f70d382ec6c5d8d27b56c4e84106ac8c55 Co-authored-by: Christian Brabandt <cb@256bit.org> Co-authored-by: Adri Verhoef <a3@a3.xs4all.nl> Co-authored-by: Viktor Szépe <viktor@szepe.net> Co-authored-by: nuid64 <lvkuzvesov@proton.me> Co-authored-by: Meng Xiangzhuo <aumo@foxmail.com> Co-authored-by: Dominique Pellé <dominique.pelle@gmail.com>
| * | vim-patch:9.0.1877: missing test for patch 9.0.1873zeertzjq2023-09-09
|/ / | | | | | | | | | | | | | | | | | | | | | | Problem: missing test for patch 9.0.1873 Solution: add a test trying to exchange windows Add a test, making sure that switching windows is not allowed when textlock is active, e.g. when running `:s/<pat>/\=func()/` https://github.com/vim/vim/commit/18d2709aa12ffa3f6ae1a13059990558c5f8e406 Co-authored-by: Christian Brabandt <cb@256bit.org>
* | ci: remove container solution for the linux runnerdundargoc2023-09-09
| | | | | | | | | | | | | | | | This will fix the failing release job. Ubuntu 18.04 is incompatible with checkout action version 4, which requires glibc 2.28+. This will bump the minimum glibc version required to use the release versions to 2.31. People requring the older releases can find them at https://github.com/neovim/neovim-releases.
* | vim-patch:86cfb39030ebChristian Clason2023-09-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | runtime(tohtml): Update TOhtml to version 9.0v2 (vim/vim#13050) Modified behavior: - Change default value of g:html_use_input_for_pc from "fallback" to "none". This means with default settings, only the standards-based method to make special text unselectable is used. The old method relying on unspecified browser behavior for <input> tags is now only used if a user specifically enables it. - Officially deprecate g:use_xhtml option (in favor of g:html_use_xhtml) by issuing a warning message when used. Bugfixes: - Fix issue vim/vim#8547: LineNr and other special highlight groups did not get proper style rules defined when using "hi link". - Fix that diff filler was not properly added for deleted lines at the end of a buffer. Other: - Refactored function definitions from long lists of strings to use :let-heredoc variable assignment instead. - Corrected deprecated "." string concatenation operator to ".." operator in more places. https://github.com/vim/vim/commit/86cfb39030eb557e1a1c7804f9c147556ca5dbf1 Co-authored-by: fritzophrenic <fritzophrenic@gmail.com>
* | vim-patch:4e554d282c50Christian Clason2023-09-09
|/ | | | | | | | runtime(perl): Update ftplugin and indent files (vim/vim#13052) https://github.com/vim/vim/commit/4e554d282c50e428932df5fff9917f8a836f7782 Co-authored-by: dkearns <dougkearns@gmail.com>
* vim-patch:9.0.1884: Wrong order of arguments for error messages (#25055)zeertzjq2023-09-09
| | | | | | | | | | Problem: Wrong order of arguments for error messages Solution: Reverse order or arguments for e_aptypes_is_null_nr_str closes: vim/vim#13051 https://github.com/vim/vim/commit/1bd2cb11694690a77e4141bce2e34d9dfb882f1c Co-authored-by: Christ van Willegen <cvwillegen@gmail.com>
* feat(runtime): highlight hl groups in syntax.txt (#25050)zeertzjq2023-09-08
| | | | | | - Add runtime/lua/vim/vimhelp.lua, which is a translation of Vim's runtime/import/dist/vimhelp.vim. - Unlike Vim, run the highlighting from an ftplugin file instead of a syntax file, so that it is run even if using treesitter.
* Merge pull request #24985 from bfredl/hash2bfredl2023-09-08
|\ | | | | refactor(map): enhanced implementation, Clean Code™, etc etc
| * refactor(map): enhanced implementation, Clean Code™, etc etcbfredl2023-09-08
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This involves two redesigns of the map.c implementations: 1. Change of macro style and code organization The old khash.h and map.c implementation used huge #define blocks with a lot of backslash line continuations. This instead uses the "implementation file" .c.h pattern. Such a file is meant to be included multiple times, with different macros set prior to inclusion as parameters. we already use this pattern e.g. for eval/typval_encode.c.h to implement different typval encoders reusing a similar structure. We can structure this code into two parts. one that only depends on key type and is enough to implement sets, and one which depends on both key and value to implement maps (as a wrapper around sets, with an added value[] array) 2. Separate the main hash buckets from the key / value arrays Change the hack buckets to only contain an index into separate key / value arrays This is a common pattern in modern, state of the art hashmap implementations. Even though this leads to one more allocated array, it is this often is a net reduction of memory consumption. Consider key+value consuming at least 12 bytes per pair. On average, we will have twice as many buckets per item. Thus old implementation: 2*12 = 24 bytes per item New implementation 1*12 + 2*4 = 20 bytes per item And the difference gets bigger with larger items. One might think we have pulled a fast one here, as wouldn't the average size of the new key/value arrays be 1.5 slots per items due to amortized grows? But remember, these arrays are fully dense, and thus the accessed memory, measured in _cache lines_, the unit which actually matters, will be the fully used memory but just rounded up to the nearest cache line boundary. This has some other interesting properties, such as an insert-only set/map will be fully ordered by insert only. Preserving this ordering in face of deletions is more tricky tho. As we currently don't use ordered maps, the "delete" operation maintains compactness of the item arrays in the simplest way by breaking the ordering. It would be possible to implement an order-preserving delete although at some cost, like allowing the items array to become non-dense until the next rehash. Finally, in face of these two major changes, all code used in khash.h has been integrated into map.c and friends. Given the heavy edits it makes no sense to "layer" the code into a vendored and a wrapper part. Rather, the layered cake follows the specialization depth: code shared for all maps, code specialized to a key type (and its equivalence relation), and finally code specialized to value+key type.
* build(vim-patch.sh): don't use control chars in command (#25044)zeertzjq2023-09-08
|
generated by cgit (git 2.34.1) at 2025-07-07 15:20:52 +0000