Open alvarosevilla95 opened 3 months ago
Observed this as well.
I have this after opening and closing the Telescope window, but not every time. It is pretty annoying as I have to restart the editor, closing all the tabs which completely disrupts the workflow.
@alvarosevilla95 @Roman- @iamim which versions of nvim are you using?
Seems like it's trying to delete the "ghost text" but out of the intended buffer. I tried with going back to alpha
(nvim dashboard), into mason
, into lazy
, into telescope
and into quickfixlist
. Also opening various buffers, windows and tabs, but I can't trigger it.
https://github.com/user-attachments/assets/28a11a88-dda7-457d-bc38-a4f66904d4c4
The text in the demo was done by adding this on top of supermaven-nvim/completion_preview:98
:
local log = require("supermaven-nvim.logger")
log:debug("------------------- buf name ---------------------")
log:debug(vim.inspect(vim.api.nvim_buf_get_name(buf)))
log:debug("------------------- buf name ---------------------")
log:debug("----------------- buf and ns_id ------------------")
log:debug(vim.inspect(buf))
log:debug(vim.inspect(self.ns_id))
log:debug("----------------- buf and ns_id ------------------")
log:debug("------------------- extmarks ---------------------")
log:debug(vim.inspect(vim.api.nvim_buf_get_extmarks(buf, self.ns_id, 0, -1, { details = true, hl_name = true, type = "virt_text" })))
log:debug("------------------- extmarks ---------------------")
:SupermavenShowLog
If you add this and can reproduce it, paste the logs so it's easier to track the error.
[!Note] You will need to add or modify the
log_level
config option in your own config.--- supermaven plugin config --- ... log_level = "debug"
Also facing this issue quite often, not sure when exactly it happens. Restarting neovim usually fixes it for me.
I've been using the plugin for a few days. Love it so far, but after a while of editing I eventually start to get this error (which triggers on pretty much every key press, making it unusuable):
I can't really figure out how reproduce reliably though, if I can I will update the issue