GNU bug report logs -
#55097
29.0.50; flymake-show-buffer-diagnostics does not enable flymake-mode
Previous Next
Reported by: No Wayman <iarchivedmywholelife <at> gmail.com>
Date: Sun, 24 Apr 2022 18:48:02 UTC
Severity: normal
Found in version 29.0.50
Fixed in version 29.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
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 55097 in the body.
You can then email your comments to 55097 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#55097
; Package
emacs
.
(Sun, 24 Apr 2022 18:48:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
No Wayman <iarchivedmywholelife <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Sun, 24 Apr 2022 18:48:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
flymake-show-buffer-diagnostics will display an empty diagnostics
buffer if flymake-mode is not enabled in that buffer. This is
confusing, as it makes it appear as if there are no issues, when
that may not be the case.
The command should either signal a user-error or (IMO better)
enable flymake mode in the buffer if it is not already enabled.
In GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.33, cairo version 1.17.6)
of 2022-04-20 built on arch
Repository revision: f98c3f4426fecf794f47f27aebe1f3b854fb1bfd
Repository branch: master
System Description: Arch Linux
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#55097
; Package
emacs
.
(Mon, 25 Apr 2022 08:08:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 55097 <at> debbugs.gnu.org (full text, mbox):
No Wayman <iarchivedmywholelife <at> gmail.com> writes:
> flymake-show-buffer-diagnostics will display an empty diagnostics
> buffer if flymake-mode is not enabled in that buffer. This is
> confusing, as it makes it appear as if there are no issues, when that
> may not be the case.
> The command should either signal a user-error or (IMO better) enable
> flymake mode in the buffer if it is not already enabled.
Commands tied to certain modes aren't supposed to be used outside of
those modes, and will usually give nonsensical results if you do that.
So this is one of those "well, don't do that, then" situations.
But on the other hand, I can see that this is a command that people
might be calling spuriously, so I've made it error out in these
situations.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
bug marked as fixed in version 29.1, send any further explanations to
55097 <at> debbugs.gnu.org and No Wayman <iarchivedmywholelife <at> gmail.com>
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Mon, 25 Apr 2022 08:08:02 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
.
(Mon, 23 May 2022 11:24:10 GMT)
Full text and
rfc822 format available.
This bug report was last modified 3 years and 114 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.