Gregory Anders

>I'm unsure how to get an optimised Lua version into Neovim. Previously I have only had to create a PR with Vim and a few days later, the Neovim team...

> Does this potentially (in the future) expand the capabilities of pipelines to work on array-like stuff? For reference, currently we have defined `:help list-iterator` and various pipeline operations say...

>I'm guessing this is due to DECRQSS terminal escapes that aren't implemented by macOS terminal. Apparently https://github.com/alacritty/alacritty/issues/7184. The terminal should not print an escape sequence just because it's unimplemented. This...

If https://github.com/neovim/neovim/pull/29197 is applied then you can opt out of the DECRQSS/XTGETTCAP queries by setting `$COLORTERM` to any value other than `truecolor` or `24bit` (e.g. `256` or `16`).

> Thanks for that PR, @gpanders . I see the PR mentions that setting `$COLORTERM` to `truecolor` or `24bit` should prevent the terminal from being queried. However, I've found that...

FYI with https://github.com/neovim/neovim/pull/31730 merged, the process for disabling the OSC 52 query has changed. Instead, use: ```lua local termfeatures = vim.g.termfeatures or {} termfeatures.osc52 = false vim.g.termfeatures = termfeatures ```

>We don't change anything. Using nil in a list is an anti-pattern ?! It does clearly have some valid and useful use cases, as we can see. So probably something...

@luukvbaal IIUC the current behavior on master is fine as-is and this PR fixes an issue when a redraw is performed in `_defaults.lua`? So kicking this to the 0.11 milestone...

>(don't ask me why) This is really the root of my hesitation to merge this pre 0.10. If it doesn't fix any user facing bugs (that we know of) in...

>Note: this is different from vim.diagnostics severity-sort.reversed, since then the order is reversed, but the highest priority signs aren't visible. Can you elaborate on this? Do you mean they are...