cannot change buffer when Flycheck Error Messages is shown #617
Comments
@soonhokong I managed to reproduce the problem. It is super weird. |
@fpvandoorn and @leodemoura, I'll take a look at this one. |
I can reproduce the problem as well. I believe this is an upstream problem because the same problem happens when I try to open a C++ file. I will open an issue in flycheck repository. |
I opened an issue at flycheck/flycheck#648. |
@fpvandoorn and @leodemoura, I have struggled with this issue. Today, I found a way to reproduce with a fresh emacs ( He also suggested many points for improvements. I'll update |
@soonhokong Should we close this one? |
@leodemoura, I believe that this is an upstream issue. I just sent this video to the author of flycheck-mode. I hope this help him fix the problem. |
Thanks! |
@leodemoura and @fpvandoorn, flycheck team confirmed that they can reproduce this problem without Lean-mode. See flycheck/flycheck#648 (comment). However, it seems that it will take some time for them to fix it. @leodemoura, please feel free to close this issue here. I'll re-open it when I hear anything from the flycheck team |
@soonhokong Thanks for investigating this issue! |
The problem is fixed by the flycheck team. I'll write another comment when the patch is arrived at MELPA. |
Great! Thanks for your efforts to create an upstream example! |
@fpvandoorn, the latest version of flycheck (20151216) is now available via MELPA. Please upgrade your flycheck and check you don't have this problem anymore. |
I updated flycheck and the problem is indeed solved. Thanks! |
Steps to reproduce:
standard.lean
is not opened in a buffer in Emacstest.lean
in thelibrary
folder, containingend
so that the*Flycheck Error Messages*
buffer is shown.standard.lean
usingC-x C-f standard.lean
.Result: The buffer
standard.lean
is opened, but the current buffer has not changed tostandard.lean
(it is stilltest.lean
)C-x C-f standard.lean
again works as expected, becausestandard.lean
is now open.(The fact that you open a
.lean
/.hlean
file seems to matter, opening other files seems to work normally).Jakob and I noticed this behavior already for a while, but we couldn't consistently reproduce it before.
The text was updated successfully, but these errors were encountered: