Skip to content
This repository has been archived by the owner on Oct 14, 2023. It is now read-only.

cannot change buffer when Flycheck Error Messages is shown #617

Closed
fpvandoorn opened this issue May 21, 2015 · 14 comments
Closed

cannot change buffer when Flycheck Error Messages is shown #617

fpvandoorn opened this issue May 21, 2015 · 14 comments
Assignees

Comments

@fpvandoorn
Copy link
Contributor

Steps to reproduce:

  1. Make sure the file standard.lean is not opened in a buffer in Emacs
  2. Create a file test.lean in the library folder, containing
variable P : nat → Type

example : P (nat.of_num 1000) :=
begin
  esimp [nat.of_num]
end
  1. In Emacs, move your point over end so that the *Flycheck Error Messages* buffer is shown.
  2. Try to open standard.lean using C-x C-f standard.lean.
    Result: The buffer standard.lean is opened, but the current buffer has not changed to standard.lean (it is still test.lean)
  3. Executing C-x C-f standard.lean again works as expected, because standard.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.

@leodemoura
Copy link
Member

@soonhokong I managed to reproduce the problem. It is super weird.
If we try multiple times, it eventually succeeds (at least for me).
If we close *Flycheck Error Messages* buffer, it also succeeds.
Any ideas?

@soonhokong soonhokong self-assigned this May 21, 2015
@soonhokong
Copy link
Contributor

@fpvandoorn and @leodemoura, I'll take a look at this one.

@soonhokong
Copy link
Contributor

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.

@soonhokong
Copy link
Contributor

I opened an issue at flycheck/flycheck#648.

@soonhokong
Copy link
Contributor

@fpvandoorn and @leodemoura, I have struggled with this issue. Today, I found a way to reproduce with a fresh emacs (emacs -q) and reported it to the flycheck author. I'll keep you posted the response.

He also suggested many points for improvements. I'll update lean-flycheck.el file by following them.

@leodemoura
Copy link
Member

@soonhokong Should we close this one?

@soonhokong
Copy link
Contributor

@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.

@leodemoura
Copy link
Member

Thanks!

@soonhokong
Copy link
Contributor

@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

@leodemoura
Copy link
Member

@soonhokong Thanks for investigating this issue!

@soonhokong
Copy link
Contributor

The problem is fixed by the flycheck team. I'll write another comment when the patch is arrived at MELPA.

@fpvandoorn
Copy link
Contributor Author

Great! Thanks for your efforts to create an upstream example!

@soonhokong
Copy link
Contributor

@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.

@fpvandoorn
Copy link
Contributor Author

I updated flycheck and the problem is indeed solved. Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants