Justin M. Keyes comments

Results 2414 comments of


                                            Justin M. Keyes

feat(statusline): nvim_eval_statusline('') returns default statusline

Great analysis, thanks. Those compromises don't sound bad to me. Let's start with what can be expressed as a self-contained 'statusline' expression and see how it behaves. If there is...

feat(statusline): nvim_eval_statusline('') returns default statusline

Can you rebase this? Try `git fetch --all && git merge --squash origin/master`

feat(statusline): nvim_eval_statusline('') returns default statusline

https://github.com/neovim/neovim/pull/33036

Volar LSP: "Can't find typescript.js or tsserverlibrary.js"

> The error occurs when typescript is not installed in the project. An installation of `vue.js` without `typescript` therefore now generates an error. What do you expect from nvim-lspconfig to...

iterm2 3.5.6+ with neovim 0.11, on FocusGained, j/k jump to top/bottom of buffer

after staring `nvim --clean`, try clearing the default TermResponse handler: :au! nvim.tty does that fix it?

iterm2 3.5.6+ with neovim 0.11, on FocusGained, j/k jump to top/bottom of buffer

Try this: nvim --clean --cmd 'lua require("vim.termcap").query = function() end' that should totally disable the terminal querying.

iterm2 3.5.6+ with neovim 0.11, on FocusGained, j/k jump to top/bottom of buffer

Can you check a previous release of iTerm2, say from 1 year ago?

iterm2 3.5.6+ with neovim 0.11, on FocusGained, j/k jump to top/bottom of buffer

The reason it started since Nvim 0.11 is likely because we do more "terminal queries". OTOH, I wonder what changed in iterm 3.5.6+

iterm2 3.5.6+ with neovim 0.11, on FocusGained, j/k jump to top/bottom of buffer

> This doesn’t reproduce on the latest iterm nightly, so I’m assuming this was a iterm2 bug that is now fixed.

iterm2 3.5.6+ with neovim 0.11, on FocusGained, j/k jump to top/bottom of buffer

> There is report on that in iterm2 (https://gitlab.com/gnachman/iterm2/-/issues/12212) but it makes no sense since there were no updates of iterm since January and the problem appeared with nvim release...