Known Issues Tracker

[folke]

• Wrong incsearch highlighting when calling nvim_buf_set_lines from timer in cmdline with conceallevel neovim/neovim#17810
  • Incsearch loses highlights during redraw
  • 🪓 we disable conceallevel during search
• vim.ui_attach: detect if a message was sent because of a redraw (with ext_messages) neovim/neovim#20416
  • redraw triggers last messages to ext_messages
  • 🪓 we wrap redraw, ignore messages and check for ui updates
• vim.ui_attach: with ext_cmdline, ext_messages want an event for user input with getchar/getcharstr neovim/neovim#20311
  • we need to know when state will become blocking
  • 🪓 we wrap input functions so we know blocking input is coming
• control the visible cursor with getchar(), vim.ui_attach+ext_cmdline, etc neovim/neovim#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
• Not compatible with neovide #17
• redraw doesn't update the UI during substitute neovim/neovim#20463
  • fix(ui): flush ext_cmdline events before doing cmdpreview neovim/neovim#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
• First echo has empty kind with ext_messages neovim/neovim#20462
  • first echo has the wrong kind
• [bag]: wrap doesn't work rcarriga/nvim-notify#137
  • nvim-notify does not wrap notifications
• Formatting of msg_show for map is missing newlines with ext_messages neovim/neovim#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 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)

[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]

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]

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.

[insidewhy]

One more, I'm not sure if it's a bug in noice/neovim or an issue with my configuration (I'm using the default configuration from lazy). I'm using neovim nightly from two nights ago and when I start/finish recording a macro I don't get any indication.

[folke]

@insidewhy check the docs. You can either get a notification or just add it to lualine

[JohnWilliston]

I have a similar problem, but I don't merely not get the notification: the recording doesn't work. Nothing is recorded. I find after trying the fixes mentioned in the docs that the code to get a notification from Noice fails in both senses; i.e., I don't get a notification I'm recording and nothing records. Whereas if I change my Lualine config to show the recording message, then I see the notification on the status line and the recording actually takes place and can be used.

[folke]

@JohnWilliston noice doesn't interfere or interact with recording macros in any way, so 10000% something in your config unrelated to noice.

[JohnWilliston]

@JohnWilliston noice doesn't interfere or interact with recording macros in any way, so 10000% something in your config unrelated to noice.

I don't know how to reconcile that with the fact that macros don't record when I'm using Noice notifications and do work when I'm not. I like Noice a lot, but I don't like it enough to give up macro recording.