Justin M. Keyes

> All I'm saying, there are better options for making temporary files, if that's what constitutes a "scratchpad" in this case. That just means plugins will have to find a...

> However, we mark a discussion about what "scratch" type should mean in Neovim "off-topic" because it's not in line with the quick hack we have in mind. Good job!...

@DarkDefender Thanks! > (In non true color mode, it would display the same base colors as the host terminal) So in that case, is there currently any way for the...

> `g:terminal_color_` was put in place so that users could change the colors displayed in true color mode to the ones that they wanted Why wouldn't the colors be the...

I think it's because vim.lsp.config assumes "single-file support" by default. If the LS doesn't support that, then the config should specify `workspace_required`: https://github.com/neovim/nvim-lspconfig/pull/3716#issuecomment-2800006283 If that fixes the issue, please send...

yes it will be in 0.11.1 you can try out the nightly: https://github.com/neovim/neovim/releases/tag/nightly

This is because of https://github.com/neovim/neovim/pull/4929#issuecomment-227501548. As I mentioned there, instead of forcing the resize at every BufEnter/WinEnter, I think instead the terminal resize should only happen on `:redraw!` / ``...

@mhinz to be clear, `:redraw!` (with bang) should be required. Non-bang `:redraw` happens far too often...

@mhinz Also I think totally reverting #4929 is not necessary. Perhaps it could be modified to resize only if the target size is greater than the previous size. That way...

@sprice-janrain It does clip text, I just tried in vim8.1: ``` :term ls ctrl-w N ctrl-w v i ```