Release 0.9 #8
Closed
Release 0.9 #8
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…-0.9 [Backport release-0.9] vim-patch:9.0.1759: Visual highlight not working with cursor at end of screen line
(cherry picked from commit e3e74c3)
…-0.9 [Backport release-0.9] fix(extmarks): wrong display when changing text with virt_lines
Fix neovim#24655 (cherry picked from commit 36108bf)
…-0.9 [Backport release-0.9] fix(statuscolumn): force full redraw when signcolumn is invalid
Problem: 'endofline' can be used to detect if a file ends of <EOL>, however editorconfig can break this. Solution: Set 'endofline' during BufWritePre Fixes: neovim#24869 (cherry picked from commit 84376af)
…-0.9 [Backport release-0.9] fix(editorconfig): do not set 'endofline'
(cherry picked from commit a94d35f)
…-0.9 [Backport release-0.9] fix(editorconfig): add missing root validation
(cherry picked from commit bcf9176)
(cherry picked from commit aa4900d)
(cherry picked from commit 5f29f7b)
…-0.9 [Backport release-0.9] fix(editorconfig): highlight properties with dashes
(cherry picked from commit f3e8942)
…-0.9 [Backport release-0.9] fix(editorconfig): only warn once on errors
adapt to upstream build system changes (rolling release)
also update highlight queries and test fixup: tests
also update highlight queries
Problem: `push_tree`, every time its called for the same TSTree with `do_copy=false` argument, creates a new userdata for it. Each userdata, when garbage collected, frees the same TSTree C object. Solution: Add flag to userdata, which indicates, should C object, which userdata points to, be freed, when userdata is garbage collected.
Unfortunately the gc=false objects can refer to a dangling tree if the gc=true tree was freed first. This reuses the same tree object as the node itself is keeping alive via the uservalue of the node userdata. (wrapped in a table due to lua 5.1 restrictions)
[backport release-0.9] fix(treesitter): fix TSNode:tree() double free
…e call nvim_buf_call (neovim#24950) fix(filetype): make sure buffer is valid before call nvim_buf_call (cherry picked from commit c3e6116) Co-authored-by: HongboLiu <lhbf@qq.com>
…on grid_line events"" This reverts commit be14ead.
Co-authored-by: bfredl <bjorn.linse@gmail.com>
It has not been used for a long time and the likelihood of it working isn't high. (cherry picked from commit 5100fe2)
(cherry picked from commit 6ddb775)
As specified by MAINTAIN.md, features should be soft deprecated at first (meaning no warnings) to give people a chance to adjust. The problem with this approach is that deprecating a feature becomes harder than usual as during the soft deprecation period you need to remember not to issue a warning, and during the hard deprecation period you need to remember to start issuing a warning. This behavior is only enforced if the `plugin` parameter is `nil` as plugins may not want this specific behavior. (cherry picked from commit 0a598c1)
Problem: `:checkhealth nvim` warns about missing vimrc if `init.lua` exists but `init.vim` does not. Solution: Check for any of: init.vim, init.lua, $MYVIMRC. Fix neovim#25291 Backport of neovim#25306
…#26887) tmux indicates its RGB support via setrgbb and setrgbf. In modern tmux code, Tc and RGB just set setrgbb and setrgbf, so we can just check for them. Link: tmux/tmux@7eb496c (cherry picked from commit 88eb0ad) Co-authored-by: Tristan Partin <tristan@partin.io>
…-0.9 [Backport release-0.9] fix(terminal): check if mouse on statusline/tabline/winbar/vsep
A lot of code inside HAVE_WORKING_LIBINTL doesn't really depend on a "working libintl". For instance ex_language is also used for ":lang collate" and ":lang time". Also ":lang C" should not fail just because translations aren't available (it just means use the default text). References: neovim#1 2d00ead separate ifdefs for locale and gettext got merged together. neovim@8253e29 Unmotivated switcharoo of get_mess_env() logic. If available, get_locale_val(LC_MESSAGES) is the correct implementation. (cherry picked from commit 3a44db5)
…-0.9 [Backport release-0.9] refactor(lang): reduce scope of HAVE_WORKING_LIBINTL #ifdefs
…eovim#26905) separate_arguments() doesn't operate in place on a variable. It expects a string argument to parse and stores the results in the specified variable. (cherry picked from commit 52e6059)
…se-0.9 [Backport release-0.9] fix(test): call separate_arguments() correctly to honor $BUSTED_ARGS (neovim#26905)
Since execl() is a variadic function, it requries a NULL-terminal to indicate the end of its argument list, c.f. exec(3) > The first argument, by convention, should point to the filename > associated with the file being executed. The list of arguments *must* > be terminated by a null pointer This fixes the failure seen on aarch64 and i386, due to garbage data being considered part of the variadic arguments. (cherry picked from commit 8861ad8)
…se-0.9 [Backport release-0.9] fix(test/tui_spec): pass the expected NULL-sentinel to execl()
…ffer size (neovim#26943) fix(tui): use buflen to calculate remaining buffer size (neovim#26942) buf is a pointer argument, not a local char array, so sizeof(buf) is just the size of a pointer type on the platform. This is always an incorrect value, but on 32-bit platforms it actually has an impact, since sizeof(buf) is just 4 and causes the buffer to get truncated. (cherry picked from commit 367e52c) Co-authored-by: James McCoy <jamessan@jamessan.com>
…-0.9 [Backport release-0.9] fix(pum): handle right-click menu repositioning with multigrid
Problem: Crash when using nested map().
Solution: Clear the pointer in prepare_vimvar(). (Ozaki Kiichi,
closes vim/vim#4890, closes vim/vim#4891)
vim/vim@27da7de
Cherry-pick Test_filter_map_nested() from patch 8.1.1964.
Co-authored-by: Bram Moolenaar <Bram@vim.org>
(cherry picked from commit a344519)
…-0.9 [Backport release-0.9] vim-patch:8.1.1968: crash when using nested map()
…modifies hidden buffer (neovim#27051) Problem: Insert mode not stopped if an autocommand modifies a hidden buffer while closing a prompt buffer. Solution: Don't set b_prompt_insert if stop_insert_mode is already set. (zeertzjq) closes: vim/vim#13872 vim/vim@9695836
…m#27071) Problem: Modifying a hidden buffer still interferes with prompt buffer mode changes. Solution: Save and restore b_prompt_insert. (zeertzjq) closes: vim/vim#13875 Modifying hidden buffer still interferes with prompt buffer mode changes vim/vim@f267847
Backport to release-0.9
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.