aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Merge pull request #25418 from bfredl/no_attr2bfredl2023-09-29
|\ | | | | refactor(message): remove more "attr" variants
| * refactor(message): smsg_attr -> smsgbfredl2023-09-29
| |
| * refactor(message): msg_puts_attr_len -> msg_puts_lenbfredl2023-09-29
| |
| * refactor(message): msg_outtrans_long_len_attr -> msg_outtrans_longbfredl2023-09-29
| |
* | docs(term): use tic -x for better compatibility with old ncurses (#25421)Dr. Matthew Swabey2023-09-29
| | | | | | Use `tic -x` instead of `tic` to include any unknown capabilities in a modern `terminfo.src` as user-defined ones, instead of dropping them. Modern ncurses behavior with `tic -x` will not change.
* | Merge pull request #25395 from bfredl/line_buf2bfredl2023-09-29
|\ \ | | | | | | refactor(grid): unify the two put-text-on-the-screen code paths
| * | refactor(grid): unify the two put-text-on-the-screen code pathsbfredl2023-09-29
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The screen grid refactors will continue until morale improves. Jokes aside, this is quite a central installment in the series. Before this refactor, there were two fundamentally distinct codepaths for getting some text on the screen: - the win_line() -> grid_put_linebuf() -> ui_line() call chain used for buffer text, with linebuf_char as a temporary scratch buffer - the grid_line_start/grid_line_puts/grid_line_flush() -> ui_line() path used for every thing else: statuslines, messages and the command line. Here the grid->chars[] array itself doubles as a scratch buffer. With this refactor, the later family of functions still exist, however they now as well render to linebuf_char just like win_line() did, and grid_put_linebuf() is called in the end to calculate delta changes. This means we don't need any duplicate logic for delta calculations anymore. Later down the line, it will be possible to share more logic operating on this scratch buffer, like doing 'rightleft' reversal and arabic shaping as a post-processing step.
* / refactor(lsp): deprecate util methods (#25400)Maria José Solano2023-09-29
|/
* refactor: remove longdundargoc2023-09-29
| | | | | long is 32-bits even on 64-bit windows which makes the type suboptimal for a codebase meant to be cross-platform.
* fix(unittests): ignore __s128 and __u128 types in ffiJames McCoy2023-09-28
| | | | | | | | | | | | | | | | | | | | | | Linux added these types to their userspace headers in [6.5], which causes unit tests to fail like ``` -------- Running tests from test/unit/api/private_helpers_spec.lua RUN vim_to_object converts true: 17.00 ms ERR test/unit/helpers.lua:748: test/unit/helpers.lua:732: (string) ' test/unit/helpers.lua:264: ';' expected near '__s128' at line 194' exit code: 256 stack traceback: test/unit/helpers.lua:748: in function 'itp_parent' test/unit/helpers.lua:784: in function <test/unit/helpers.lua:774> ``` Since we don't use these types, they can be ignored to avoid LuaJIT's C parser choking on them. [6.5]: https://github.com/torvalds/linux/commit/224d80c584d3016cb8d83d1c33914fdd3508aa8c
* vim-patch:02902b547bdb (#25406)zeertzjq2023-09-29
| | | | | | | runtime(doc): text-objects: document how escaped delimiters are handled https://github.com/vim/vim/commit/02902b547bdb3ba480a52c90dce742201241f224 Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:9.0.1950: Vim9: error codes spread out (#25405)zeertzjq2023-09-29
| | | | | | | | | | | | | | Problem: Vim9: error codes spread out Solution: group them together and reserve 100 more for future use Reserve 100 error codes for future enhancements to the Vim9 class support closes: vim/vim#13207 https://github.com/vim/vim/commit/413f83990f15d5d59d27ab741670f527a7a3feb8 Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
* Merge pull request #25398 from zeertzjq/vim-9.0.1946zeertzjq2023-09-29
|\ | | | | vim-patch:9.0.{0607,1946,1947}: filename expansion using ** in bash may fail
| * vim-patch:9.0.1947: Bash Expansion test fails on Windows/MacOSzeertzjq2023-09-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Bash Expansion test fails on Windows/MacOS Solution: Disable Test_glob_extended_bash for now This test doesn't work on Windows even if bash can be executed, since the globstar functionality has only been enabled in Unix builds of Vim (Commit 9eb1ce531527a7177d16373b0f8689bbcd3d5f73, patch 9.0.1946). closes: vim/vim#13205 https://github.com/vim/vim/commit/03ca4002c1dcd34c4b17fe4a491b02d77ec2c887 Co-authored-by: Ken Takata <kentkt@csc.jp>
| * vim-patch:9.0.1946: filename expansion using ** in bash may failzeertzjq2023-09-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: filename expansion using ** in bash may fail Solution: Try to enable the globstar setting Starting with bash 4.0 it supports extended globbing using the globstar shell option. This makes matching recursively below a certain directory using the ** pattern work as expected nowadays. However, we need to explicitly enable this using the 'shopt -s globstar' bash command. So let's check the bash environment variable $BASH_VERSINFO (which is supported since bash 3.0 and conditionally enable the globstar option, if the major version is at least 4. For older bashs, this at least shouldn't cause errors (unless one is using really ancient bash 2.X or something). closes: vim/vim#13002 closes: vim/vim#13144 https://github.com/vim/vim/commit/9eb1ce531527a7177d16373b0f8689bbcd3d5f73 Co-authored-by: Christian Brabandt <cb@256bit.org>
| * vim-patch:9.0.0607: verbose echo message test fails on Mac OSzeertzjq2023-09-29
|/ | | | | | | | | Problem: Verbose echo message test fails on Mac OS. Solution: Skip the test on Mac OS. https://github.com/vim/vim/commit/f802767df7b4532651fcf11d49e812ead32db45b Co-authored-by: Bram Moolenaar <Bram@vim.org>
* test: decoration provider with wrapped lines (#25404)zeertzjq2023-09-28
|
* docs: Lua docstrings guidance #25345dundargoc2023-09-27
| | | | | | Recommend adding a space after i.e. `--- @see`. The "space" variant is common for the vast majority of docstring formats such as doxygen, javadoc and typescript.
* Merge pull request #25396 from bfredl/no_attrbfredl2023-09-27
|\ | | | | refactor(messages): fold msg() functions with and without attr
| * refactor(messages): rename msg_trunc_attr and msg_multiline_attr without attrbfredl2023-09-27
| |
| * refactor(messages): fold msg_attr into msgbfredl2023-09-27
| | | | | | | | | | problem: there are too many different functions in message.c solution: fold some of the functions into themselves
| * refactor(messages): fold msg_outtrans_attr into msg_outtransbfredl2023-09-27
| | | | | | | | | | problem: there are too many different functions in message.c solution: fold some of the functions into themselves
* | vim-patch:5277cfaf8afe (#25397)zeertzjq2023-09-28
| | | | | | | | | | runtime(doc): mention mouse scrolling in scrollbind-quickadj (vim/vim#13190) https://github.com/vim/vim/commit/5277cfaf8afe847b7d4dcde6057fbecb001ab64e
* | vim-patch:54f70cf0780aChristian Clason2023-09-27
| | | | | | | | | | | | | | | | runtime(swayconfig): Update syntax file (vim/vim#13192) https://github.com/vim/vim/commit/54f70cf0780a797efaf0ff9fd4190215a3ff0eb7 Co-authored-by: Josef Litoš <54900518+JosefLitos@users.noreply.github.com>
* | vim-patch:02774f99cebcChristian Clason2023-09-27
| | | | | | | | | | | | | | | | runtime(i3config): update i3config syntax (vim/vim#13191) https://github.com/vim/vim/commit/02774f99cebcb890d3861febc1d03e75c02cc92d Co-authored-by: Josef Litoš <54900518+JosefLitos@users.noreply.github.com>
* | vim-patch:347459423903Christian Clason2023-09-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | runtime(rmd) Update ftplugin and syntax files (vim/vim#13193) ftplugin/rmd.vim: - Set 'commentstring' dynamically according to code region. syntax/rmd.vim: - Include syntax highlighting of fenced languages dynamically. - Add conceal char for line break. https://github.com/vim/vim/commit/34745942390383ec626b168e9837d284622c7bbe Co-authored-by: Jakson Alves de Aquino <jalvesaq@gmail.com>
* | feat: NVIM_APPNAME supports relative paths #25233Rory Nesbitt2023-09-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: NVIM_APPNAME does not allow path separators in the name, so relative paths can't be used: NVIM_APPNAME="neovim-configs/first-config" nvim NVIM_APPNAME="neovim-configs/second-config" nvim Solution: Let NVIM_APPNAME be a relative path. Absolute paths are not supported. fix #23056 fix #24966
* | fix(clang): null pointer dereference in parse_msgpack #25389nwounkn2023-09-27
|/
* Merge pull request #25374 from bfredl/batchupdatebfredl2023-09-27
|\ | | | | refactor(grid): use batched updates for more things
| * refactor(grid): use batched updates for statusline and rulerbfredl2023-09-27
| |
| * refactor(grid): use batched updates for builtin tablinebfredl2023-09-26
| |
| * refactor(grid): use batched updates for horizontal wildmenubfredl2023-09-26
| |
* | vim-patch:8.2.3467: CursorHoldI event interferes with "CTRL-G U" (#25383)zeertzjq2023-09-27
| | | | | | | | | | | | | | | | | | Problem: CursorHoldI event interferes with "CTRL-G U". (Naohiro Ono) Solution: Restore the flag for "CTRL-G U" after triggering CursorHoldI. (closes vim/vim#8937) https://github.com/vim/vim/commit/5a9357d0bff9059f547906d8d03b31bca7215af1 Co-authored-by: Bram Moolenaar <Bram@vim.org>
* | vim-patch:8.2.3517: TextChanged does not trigger after TextChangedI (#25384)zeertzjq2023-09-27
| | | | | | | | | | | | | | | | | | Problem: TextChanged does not trigger after TextChangedI. Solution: Store the tick separately for TextChangedI. (Christian Brabandt, closes vim/vim#8968, closes vim/vim#8932) https://github.com/vim/vim/commit/db3b44640d69ab27270691a3cab8d83cc93a0861 Co-authored-by: Christian Brabandt <cb@256bit.org>
* | fix(extmarks): draw TAB in virt_text properly with 'rl' (#25381)zeertzjq2023-09-27
| |
* | refactor(tutor): cleanupJustin M. Keyes2023-09-26
| |
* | fix(tutor): Tutor steps don't work on Windows #25251Leonardo Mello2023-09-26
| | | | | | | | | | | | | | | | | | Problem: Some steps in :Tutor don't work on Windows. Solution: Add support for `{unix:...,win:...}` format and transform the Tutor contents depending on the platform. Fix https://github.com/neovim/neovim/issues/24166
* | Merge pull request #25229 from glepnir/20323bfredl2023-09-26
|\ \ | |/ |/| fix(highlight): add force in nvim_set_hl
| * fix(highlight): add force in nvim_set_hlglepnir2023-09-26
| |
* | fix(meta): add nil return types to lpeg functionsMaria José Solano2023-09-26
| |
* | fix(meta): cleanup lpeg operatorsMaria José Solano2023-09-26
| |
* | vim-patch:54e1f56cf2a5Christian Clason2023-09-26
| | | | | | | | | | | | | | | | runtime(sh): only invoke bash help in ftplugin if it has been detected to be bash (vim/vim#13171) https://github.com/vim/vim/commit/54e1f56cf2a5f74ee11baba170afff867e5d9f99 Co-authored-by: Eisuke Kawashima <e-kwsm@users.noreply.github.com>
* | fix(runtime): add commentstring for D ftplugin (#25362)ricardaxel2023-09-26
| | | | | | | | | | | | | | | | Problem: No commentstring is set for D buffers after removing the default C-style commentstring Same solution than neovim#23039 Co-authored-by: Axel Ricard <axel.ricard@allegrodvt.com>
* | Merge pull request #25360 from bfredl/bigmessbfredl2023-09-25
|\ \ | | | | | | refactor(options)!: graduate some more shortmess flags
| * | refactor(options)!: graduate some more shortmess flagsbfredl2023-09-25
|/ / | | | | | | | | | | | | | | A lot of updated places in the docs were already incorrect since long since they did not reflect the default behaviour. "[dos format]" could've been argued being better for discoverability but that ship has already sailed as it is no longer displayed by default.
* | Merge pull request #25359 from bfredl/longmessbfredl2023-09-25
|\ \ | | | | | | refactor: remove 'shortmess' save/restore panic for ex commands
| * | refactor: remove 'shortmess' save/restore panic for ex commandsbfredl2023-09-25
| | | | | | | | | | | | | | | | | | This was only used to avoid the effect of SHM_OVERALL. This can easily be handled in isolation, instead of clearing out all of 'shortmess' which has unwanted side effects and mystifies what really is going on.
* | | build(deps): bump luajit to HEAD - becf5cc65Christian Clason2023-09-25
|/ /
* | Merge pull request #25344 from gpanders/doc-shortmessbfredl2023-09-25
|\ \ | | | | | | docs: remove "f" from default 'shortmess' value
| * | docs: remove more references to shm-fGregory Anders2023-09-24
| | |