-
-
Notifications
You must be signed in to change notification settings - Fork 146
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
Setting cmdline to "neovim" doesn't disable firenvim's external cmdline #1442
Comments
Hi, thanks a lot for the interesting bug report :). The settings you provided do disable Firenvim's command line, the problem is that Noice re-enables it. This is a fundamental issue at the neovim level: Noice attaches to Neovim and pretends to be a UI, but Neovim does not support providing different command line representations to differents UIs. The workaround for current Firenvim versions is to only enable Noice when Nice colorscheme btw :) |
I was just struggling with this one myself the other day too. I've been trying to get noice spun up in my own config, but having trouble with it in two places: Firenvim and Neovide (Rust based graphical wrapper, noice related conflict info in this issue). I am able to disable it for the places it is trouble of course, but it would be nice to actually use with Firenvim. As such the mentioned |
Fusing messages and cmdline isn't ideal, but as neovim doesn't offer a way to get separate cmdline and messages, it's probably better not to offer a second configuration option that only works conditional on the "cmdline" setting.
Fusing messages and cmdline isn't ideal, but as neovim doesn't offer a way to get separate cmdline and messages, it's probably better not to offer a second configuration option that only works conditional on the "cmdline" setting.
|
What I tried to do
I am trying to disable the external cmdline from firenvim so I can use the interface from noice.nvim instead.
I've set the local settings:
What happened
Firenvim's cmdline appears on top of Noice's:
The text was updated successfully, but these errors were encountered: