emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#29176: closed (26.0.90: [FLYMAKE] incorrect mode l


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#29176: closed (26.0.90: [FLYMAKE] incorrect mode line indicator)
Date: Thu, 09 Nov 2017 20:47:02 +0000

Your message dated Thu, 09 Nov 2017 20:46:26 +0000
with message-id <address@hidden>
and subject line Re: bug#29176: 26.0.90: [FLYMAKE] incorrect mode line indicator
has caused the debbugs.gnu.org bug report #29176,
regarding 26.0.90: [FLYMAKE] incorrect mode line indicator
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
29176: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=29176
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 26.0.90: [FLYMAKE] incorrect mode line indicator Date: Mon, 06 Nov 2017 09:43:25 -1100
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.



--- End Message ---
--- Begin Message --- Subject: Re: bug#29176: 26.0.90: [FLYMAKE] incorrect mode line indicator Date: Thu, 09 Nov 2017 20:46:26 +0000 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.90 (gnu/linux)
address@hidden (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


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]