Slow or fail to exit when Python code is executed after GuiClose #394
Comments
|
Possibly related to #341. |
equalsraf
pushed a commit
that referenced
this issue
Jul 25, 2018
If the shim is running the VimLeave event sends a notification to the Gui (GuiClose) so that it shuts down too. This notification triggers the neovimGuiCloseRequest which causes the main window to call Shell::close() which in turn calls "qa". So a loop is established where nvim calls the GUI to shutdown and the GUI calls "qa" that triggers again the notification. Avoid this with a boolean flag in the main window i.e. if a closeEvent is triggered in the main window, and nvim already requested a close, just close the window.
|
Does #435 fix this for you? |
|
It does. Thanks! |
|
Merged into master. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When Python code is executed after the
GuiClosefunction, nvim-qt takes several seconds to exit or does not exit at all with the messagePress Enter or type command to continueon the command line. Pressing the enter key twice will then exit Neovim.Steps to reproduce:
nvim-qt -- -u NORC:autocmd VimLeave * python pass(replacepython passwithpython3 passif using Python 3):qHere are the logs from these steps with
set verbose=15. Looks like Neovim gets into an infinite loop calling alternativelyGuiCloseandpython pass.Related issue: ycm-core/YouCompleteMe#2919.
Configuration:
v0.2.3-711-g6c3dd51aa;neovimPython package 0.2.1.The text was updated successfully, but these errors were encountered: