From: Eli Zaretskii <eliz@gnu.org>
To: "Aidan Beggs" <nadiasggeb001@gmail.com>,
"João Távora" <joaotavora@gmail.com>
Cc: 40529@debbugs.gnu.org
Subject: bug#40529: 26.3; global-display-line-numbers-mode and flymake-show-diagnostics-buffer error
Date: Fri, 10 Apr 2020 09:30:20 +0300 [thread overview]
Message-ID: <83v9m7n98j.fsf@gnu.org> (raw)
In-Reply-To: <CAEF3qkJiWgAf9A=_t1B8ii1b=-poGc1=f7PC5BFk_p2ibyUX8g@mail.gmail.com> (message from Aidan Beggs on Thu, 9 Apr 2020 16:55:44 -0400)
> From: Aidan Beggs <nadiasggeb001@gmail.com>
> Date: Thu, 9 Apr 2020 16:55:44 -0400
>
> emacs -Q
> C-x b *scratch*
> M-x global-display-line-numbers-mode
> M-x flymake-mode
> M-x flymake-show-diagnostics-buffer
João, here are the results of my preliminary investigation into this,
as posted on Reddit (where this was first reported), I hope they will
be helpful:
Under the above settings, flymake--diagnostics-buffer-entries is
invoked as side effect of calling flymake-diagnostics-buffer-mode from
flymake-show-diagnostics-buffer, and at that point
flymake--diagnostics-buffer-source has not yet been set to a valid
buffer name. So the with-current-buffer form at the beginning of
flymake--diagnostics-buffer-entries barfs.
Thanks.
next prev parent reply other threads:[~2020-04-10 6:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 20:55 bug#40529: 26.3; global-display-line-numbers-mode and flymake-show-diagnostics-buffer error Aidan Beggs
2020-04-10 6:30 ` Eli Zaretskii [this message]
2020-04-10 11:50 ` João Távora
2020-04-10 12:16 ` Eli Zaretskii
2020-04-10 14:38 ` João Távora
2020-04-10 15:50 ` Eli Zaretskii
2020-04-10 16:09 ` João Távora
2020-04-10 16:16 ` João Távora
2020-04-12 12:22 ` João Távora
2020-04-12 13:43 ` Eli Zaretskii
2020-04-12 14:13 ` João Távora
2020-04-12 14:42 ` Eli Zaretskii
2020-04-12 16:58 ` João Távora
2020-04-12 17:15 ` Eli Zaretskii
2020-04-12 20:45 ` Aidan Beggs
2020-04-13 5:03 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83v9m7n98j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=40529@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=nadiasggeb001@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).