You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to play nice with other plugins that open windows: I'd like Fidget to avoid rendering over those windows (or at least do something to avoid unreadable output). See j-hui/fidget.nvim#163 for an example of this issue with nvim-tree.
Fidget suffers the same problem with Trouble windows.
Describe the solution you'd like
I'd like Trouble to expose some events that fire when the Trouble window is opened, closed, and resized (similar to what nvim-tree does).
Describe alternatives you've considered
I considered listening for Neovim's WinNew and WinResize events, but it would be very difficult to distinguish the events fired for windows that Fidget should render over (e.g., another user-created text buffer) versus the ones it shouldn't (e.g., a Trouble window).
Additional context
No response
The text was updated successfully, but these errors were encountered:
Did you check the docs?
Is your feature request related to a problem? Please describe.
Hey there 馃憢 I'm the author for fidget.nvim.
I'm trying to play nice with other plugins that open windows: I'd like Fidget to avoid rendering over those windows (or at least do something to avoid unreadable output). See j-hui/fidget.nvim#163 for an example of this issue with nvim-tree.
Fidget suffers the same problem with Trouble windows.
Describe the solution you'd like
I'd like Trouble to expose some events that fire when the Trouble window is opened, closed, and resized (similar to what nvim-tree does).
Describe alternatives you've considered
I considered listening for Neovim's
WinNew
andWinResize
events, but it would be very difficult to distinguish the events fired for windows that Fidget should render over (e.g., another user-created text buffer) versus the ones it shouldn't (e.g., a Trouble window).Additional context
No response
The text was updated successfully, but these errors were encountered: