-
Notifications
You must be signed in to change notification settings - Fork 67
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
bug: snacks_notification gets written to a new buffer #275
Comments
What do you mean with the progress message commit notification? |
My gut feeling was that this behavior was caused by snacks since if I disable it the behavior stops. When I re-enable snacks the behavior comes back. The unwritten buffer is of type snacks_notification (attached screenshot). |
It seems to be some kind of a conflict with other plugins in my configuration. I added: I also disabled the telescope notify extension, noice, and nvim-notify Now the behavior is gone. I am not quite sure if it was necessary to remove noice. Seems like the error was partly in my setup and how snacks handles conflicting configuration of vim.notify, I might be wrong though. Thank you for your effort Folke, it is appreciated. |
This is not correct: vim.notify = function(msg, opts)
Snacks.notify(msg, opts)
end Just set |
@saitharun14 I have been trying to figure out why this happens. At first I thought that my configuration has a flaw that I am not able to figure out. But now that you also are seeing this behavior, with a different configuration (I suppose), I am even more curious as to what could be causing this. |
Since you're both seeing this happening with neogit, that seems to be the culprit. |
Neogit behaves as expected when I disable snacks in my configuration, preventing messages from being written to new buffers. This is a catch-22 since both Neogit and Snacks work fine when loaded alone, without the other plugin present. Reporting this as a bug to either plugin is challenging since this behavior only exists when both are loaded simultaneously. |
I will have another look at this during Christmas and see if I can figure out why this happens. Hope you both get a relaxing Christmas break. |
Yes, my configuration is different from the configuration you attached in the details. Similar to your observation, when I use them individually I don't observe the issue. |
I think that I might have figured it out. There is an option in neogit that is not part of the plugin documentation 'process_spinner = false,'. After setting that in my plugin configuration I have had no problems with buffers etc. As usual folke was spot on ;-) Here is the complete configuration for reference in case anyone else finds this thread, looking for a solution to a problem that is not related to snacks: https://github.com/ThorstenRhau/neovim/blob/main/lua/plugins/neogit.lua |
Hi @ThorstenRhau, setting process_spinner to false works but this will complete remove the processing indicator. This wan't an issue with noice, so I believe there can be a better solution. I may be wrong as I'm new to nvim. |
This resolves the issue for me. |
Did you check docs and existing issues?
Neovim version (nvim -v)
NVIM v0.10.2 Build type: Release LuaJIT 2.1.1732813678
Operating system/version
macOS 15.2 Sequoia
Describe the bug
Thank you for creating snacks, it is awesome :-)
When committing to git with neogit (https://github.com/NeogitOrg/neogit) the commit message progress notification is written to a new buffer in nvim. I believe that this is done by snacks_notify. For me this buffer is undesirable since it prevents me from exiting nvim with :q, I do not want to quit with :qa! because of the risk of loosing unsaved work.
Steps To Reproduce
Expected Behavior
No messages should be written to a new buffer.
Repro
The text was updated successfully, but these errors were encountered: