From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: 44746@debbugs.gnu.org, stefan@marxist.se
Subject: bug#44746: 28.0.50; [feature/native-comp] Noisy "*Warnings*" buffer shown on start
Date: Fri, 26 Feb 2021 16:52:30 +0200 [thread overview]
Message-ID: <83y2faq3td.fsf@gnu.org> (raw)
In-Reply-To: <xjfwnuugb01.fsf@sdf.org> (message from Andrea Corallo on Fri, 26 Feb 2021 14:27:26 +0000)
> From: Andrea Corallo <akrl@sdf.org>
> Cc: 44746-done@debbugs.gnu.org, stefan@marxist.se
> Date: Fri, 26 Feb 2021 14:27:26 +0000
>
> > Btw, I think the doc string of comp-async-report-warnings-errors could
> > use some love: as it stands now, I needed to read the code where it is
> > used to understand what it does, and why it is a defcustom. Some of
> > the explanation you, Andrea, wrote in this thread could find its way
> > into the doc string and make it much more clear.
>
> Right I tried with ad74b1b2b6, please have a look an let me know in
> case.
Thanks, it was very good. I made some minor improvements (the main of
which is to tell that people who are annoyed by the warnings should
set this to a nil value).
next prev parent reply other threads:[~2021-02-26 14:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 0:50 bug#44746: 28.0.50; [feature/native-comp] Noisy "*Warnings*" buffer shown on start Stefan Kangas
2020-11-20 8:31 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-25 22:58 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-25 23:59 ` Stefan Kangas
2021-02-26 7:19 ` Eli Zaretskii
2021-02-26 17:26 ` Stefan Kangas
2021-02-26 7:17 ` Eli Zaretskii
2021-02-26 14:27 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-26 14:52 ` Eli Zaretskii [this message]
2021-02-26 18:56 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y2faq3td.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44746@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=stefan@marxist.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.