-
Notifications
You must be signed in to change notification settings - Fork 11
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
An issue occurred while closing a buffer that is still in use #50
Comments
Hm, E315: ml_get is typically an issue internally with neovim. Regardless, if it's being triggered by capturing a new node and it's related to closing the capture buffer, this is probably an issue to file with nvim-orgmode or neovim itself. This plugin uses nvim-orgmode to capture nodes. @kristijanhusak any thoughts here? I remember hitting this error at some point with nvim-orgmode as well. |
Similar thing was reported here nvim-orgmode/orgmode#758. Does it happen without noice? Edit: Also, which Neovim version is this? |
Reporter says neovim 0.10. I've encountered on 0.9.5. |
@kristijanhusak is there a way to transfer this issue over to the orgmode repo? If not, I'll close this out and we can piggyback on the issue you brought up earlier. |
@chipsenkbeil we can use the one I linked. |
When I encountered the issue, I didn't have noice installed, but I haven't run into it in awhile and may have avoided it with some scheduling. Let's move the conversation to your issue. |
Hello! Thank you very much for sharing!
I'm configuration of arhclinx+dwm+kitty+neovim10.0+Lazyvim
I create a new node that can only be recorded in a temporary file. Buffer needs to be closed to trigger confirmation.
There is no information in the prompt box, and there are too many error messages to close. I closed noicn.vim, but there was still an error message
error message is reported:
E315: ml_get: Invalid lnum: 1
noice.nvim ....local/share/nvim/lazy/nui.nvim/lua/nui/popup/border.lua:502: Vim:E937: Attempt to delete a buffer that is in use: /tmp/nvim.aaha/QhdcKG/3.org
The text was updated successfully, but these errors were encountered: