-
Notifications
You must be signed in to change notification settings - Fork 1.1k
E924: Current window was closed #1929
Comments
What version of syntastic are you using, what version of Vim, and what OS? Can you reproduce the problem with all other plugins disables? |
And after I disabling all other plugins, this problem still produced. |
Can you reproduce the problem with Vim instead of Neovim? |
Yes, still reproduced in VIM. |
I'm afraid I can't reproduce it with Vim. Do you have a minimal working example that illustrates the problem? What other syntastic settings are you using? |
https://github.com/XadillaX/_vimrc Here's my VIM configuration files, you can delete all other plugins. https://github.com/XadillaX/aliyun-ons This is the code repo. Just open an |
How's the result? |
Well, I asked for a minimal working example, and you gave me a config consisting of 45 files. Let's put it like this: I might be able to go over all that and isolate the problem one of these years, eventually. On the other hand, I have a sketch of an idea of how what you describe could happen, essentially relating it to the Vim 7.4.1640 trainwreck (cf. #1127). If that turns out to be the real problem, your best hope would be to get it fixed in Vim. But my conjecture is still hard to check without an actual working example. Oh well. |
Same issue here:
OS: GNU/Linux (Arch Linux derivative) x64.
Well, I'm using Neovim & Syntastic on C project. The first time this error is shown the paths in the location-list are relative, for example:
Then, I reopen the document (C file with errors), save the changes without making any changes and the paths in the location-list become absolute, allowing me to access the header file without problems.
Here a poor screencast, I hope to be helpful: Best regards. |
@icaroperseo What you're showing here is an error in another plugin (perhaps clickable.vim, from a quick search on the names of the functions involved). Please report back only if you can reproduce the problem with plain Vim, with all plugins disabled except syntastic. |
OS: GNU/Linux (Arch Linux derivative) x64.
vimrc:
The issue continues, with a caveat, if I re-open the c file, save without modifying and access the location-list now the following error appears:
Regards. |
@icaroperseo The status line in your screenshot looks suspiciously like one produced by Never mind though, you're now illustrating a bug introduced in Vim 7.4.1640 (please see #1127 for details and relevance to syntastic). There were changes affecting that code since Vim 8.0.628 (the current version at the time of this writing is 8.0.692). I don't think the problem is fixed though. |
You're right, It's powerline for bash/zsh & tmux, no by vim. Anyway, I hope you can solve the issue, syntastic it's a must have, thank you and good luck! If I can help with anything else do not hesitate to ask. Best regards. |
@icaroperseo Like I said, it's a bug in Vim, not in syntastic. |
When I use
If I'm on a
.cpp
file that has error(s), after going to the error position which on another.h
header file, it will causeE924: Current window was closed
.But If I use
This error will disappear.
But another problem appeared: the error window won't close automatically even if I switch to a file that has no error.
The text was updated successfully, but these errors were encountered: