Known Issues Tracker

[folke]

• [x] https://github.com/neovim/neovim/issues/17810
  • Incsearch loses highlights during redraw
  • 🪓 we disable conceallevel during search
• [ ] https://github.com/neovim/neovim/issues/20416
  • redraw triggers last messages to ext_messages
  • 🪓 we wrap redraw, ignore messages and check for ui updates
• [ ] https://github.com/neovim/neovim/issues/20311
  • we need to know when state will become blocking
  • 🪓 we wrap input functions so we know blocking input is coming
• [x] https://github.com/neovim/neovim/issues/20309
  • we need a way to control the visible cursor without switching windows/buffers/cursors
  • 🪓 we render fake cursors instead
• [ ] plugins that rely on the cmdline position (like cmp) don't know the real cmdline position
  • 🪓 Noice fixes this for nvim-cmp
• [x] https://github.com/folke/noice.nvim/issues/17
• [x] https://github.com/neovim/neovim/issues/20463
  • [ ] https://github.com/neovim/neovim/pull/27950
  • moving the cursor during substitute does not update the cmdline ui
  • 🪓 we do vim.api.nvim_input("<space><bs>") during substitute to force a redraw
• [x] https://github.com/neovim/neovim/issues/20462
  • first echo has the wrong kind
• [x] https://github.com/rcarriga/nvim-notify/issues/137
  • nvim-notify does not wrap notifications
• [x] https://github.com/neovim/neovim/issues/20715

[ilan-schemoul]

Another known issue acknowledged by the neovim's team is that this plugin might lead to assert failures (and so crash on startup). See https://github.com/neovim/neovim/issues/28331.

By the way the readme reads "It is highly recommended to use Neovim nightly, since a bunch of issues have already been fixed upstream." however nightly releases are shipped with RelWithDebInfo mode which (I believe but cannot find documentation about this) enables assertions checks which might fail because of Noice (I have checked that Release mode doesn't crash but RelWithDebInfo crashes)

[justinmk]

however nightly releases are shipped with RelWithDebInfo mode which (I believe but cannot find documentation about this) enables assertions checks which might fail because of Noice

Assertions declare conditions that "cannot happen". Without the assertions, behavior is just undefined and may silently lead to very weird and potentially destructive situations.

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue was closed because it has been stalled for 7 days with no activity.

[bew]

Hum this looks like a mistake 🤔

[dbieber-rfideas]

Another known issue acknowledged by the neovim's team is that this plugin might lead to assert failures (and so crash on startup). See neovim/neovim#28331.

By the way the readme reads "It is highly recommended to use Neovim nightly, since a bunch of issues have already been fixed upstream." however nightly releases are shipped with RelWithDebInfo mode which (I believe but cannot find documentation about this) enables assertions checks which might fail because of Noice (I have checked that Release mode doesn't crash but RelWithDebInfo crashes)

Does anyone know what we can do about this? I am not finding solutions, but maybe I am missing something. I am ok nerfing Noice if that is required, but would prefer not to completely disable the plugin. I've tried the latest nightly as of today and it's still crashing with the latest version of Noice from Lazy.