Getting very strange behavior when starting Neotree from Hydra.nvim #1243
-
With the latest neovim nightly, I am now seeing odd behavior when launching the This strange behavior is as follows
I am looking into both of these issues from the hydra side right now, but wanted to know if anyone here had any ideas as to what might be causing neotree to misbehave when it is opened from a command fired in a floating window (I have no idea if that is the problem, just taking a shot in the dark). Hydra does some fuckery under the hood that I don't quite understand yet and I am hoping that between me digging into that and someone (maybe @cseickel) here might be able to be like "ya that is likely happening because Please note that I am not requesting help debugging this (though feel free to provide it if you know what I am missing), more so I am asking if anyone has any idea what the fuck I am seeing lol. Here's some videos showcasing the issues https://github.com/nvim-neo-tree/neo-tree.nvim/assets/2640668/d3edad80-4c8e-4cb4-9f66-3b4ea5cbcc56 The hydra command being ran is simply |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
I guess using |
Beta Was this translation helpful? Give feedback.
Figured it out!
I guess using
vim.o.eventignore
before floating window creation breaks shit now. Idk, I don't really understand why they were using that in the first place. In any case, that option is what was causing neotree to act weird when opened via hydra.