-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
plugin breaks kitty protocol (existing workaround) #181
Comments
Anyhow, I have a more minimal reproducible and it looks like "Disable the colored cursor" fixes the problem: require('material').setup({
disable = {
colored_cursor = true, -- Disable the colored cursor (enabled colored cursor breaks things)
},
}) I could reduce some more functions and it looks like the cleanup is somehow messed up: M.load = function()
vim.g.colors_name = "material"
vim.opt.termguicolors = true
vim.opt.background = "dark"
vim.opt.guicursor = "n-v-c-sm:block,i-ci-ve:ver25,r-cr-o:hor20,a:Cursor/Cursor"
local exit_group = vim.api.nvim_create_augroup("MaterialExit", { clear = true })
vim.api.nvim_create_autocmd("ExitPre", {
command = "autocmd ExitPre * set guicursor=n-v-c-sm:block,i-ci-ve:ver25,r-cr-o:hor20",
group = exit_group
})
-- apply highlights one by one
for _, highlights_fn in pairs(highlights.main_highlights) do
for name, values in pairs(highlights_fn()) do
vim.api.nvim_set_hl(0, name, values)
end
end
end |
Yes, I suspected that it would be the cursor. When the colorscheme changes the cursor color and you exit nvim, the cursor color stays the same. That autogrup is there to revert the cursor back to it's default color before nvim exits. For some reason Kitty just doesn't play nice with this option. I think it's an issue between neovim and kitty but I'll look into this in the next couple of days. The solution, for now, is to disable the colored cursor as you already found out. I'll keep you updated. |
Minimal reproducible:
Yet unhelpful manifestation: Executing
nvim --clean -u mini.lua -c quit
breaks ghostty.I will update this issue with more information how to debug/inspect the underlying issue based on provided feedback.
The text was updated successfully, but these errors were encountered: