GNU bug report logs -
#29176
26.0.90: [FLYMAKE] incorrect mode line indicator
Previous Next
Reported by: charles <at> aurox.ch (Charles A. Roelli)
Date: Mon, 6 Nov 2017 20:42:01 UTC
Severity: normal
Found in version 26.0.90
Done: joaotavora <at> gmail.com (João Távora)
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 29176 in the body.
You can then email your comments to 29176 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#29176
; Package
emacs
.
(Mon, 06 Nov 2017 20:42:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
charles <at> aurox.ch (Charles A. Roelli)
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Mon, 06 Nov 2017 20:42:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
M-x find-library RET find-func RET
M-x flymake-mode RET
After some time, [0 0 5] shows up next to "Flymake" in the mode line,
indicating 0 errors/warnings and 5 "notes".
Now type an open parenthesis. The mode line shows "Flymake[1 0]".
Undo the change, and it then shows "Flymake[0 0]". Why does it not
show "[0 0 5]" as before? If you toggle flymake-mode off and then on
again, it fixes the issue temporarily.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#29176
; Package
emacs
.
(Thu, 09 Nov 2017 20:47:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 29176 <at> debbugs.gnu.org (full text, mbox):
charles <at> aurox.ch (Charles A. Roelli) writes:
> M-x find-library RET find-func RET
> M-x flymake-mode RET
>
> After some time, [0 0 5] shows up next to "Flymake" in the mode line,
> indicating 0 errors/warnings and 5 "notes".
>
> Now type an open parenthesis. The mode line shows "Flymake[1 0]".
> Undo the change, and it then shows "Flymake[0 0]". Why does it not
> show "[0 0 5]" as before? If you toggle flymake-mode off and then on
> again, it fixes the issue temporarily.
The function checkdoc-current-buffer may error if there are unbalanced
parens, for example, but this shouldn't disable the
elisp-flymake-checkdoc backend.
Fixed in 72e62d3fdb2b24dd9808f49fbbd864715337d2bf.
Thanks,
João
Reply sent
to
joaotavora <at> gmail.com (João Távora)
:
You have taken responsibility.
(Thu, 09 Nov 2017 20:47:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
charles <at> aurox.ch (Charles A. Roelli)
:
bug acknowledged by developer.
(Thu, 09 Nov 2017 20:47:03 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Fri, 08 Dec 2017 12:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 7 years and 256 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.