unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 09:17:37 +0200	[thread overview]
Message-ID: <83o8g7qovi.fsf@gnu.org> (raw)
In-Reply-To: <xjf5z2fhhzl.fsf@sdf.org> (bug-gnu-emacs@gnu.org)

> Cc: stefan@marxist.se
> Date: Thu, 25 Feb 2021 22:58:54 +0000
> From:  Andrea Corallo via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> To complete this answer, ATM is possible to gate all warnings reported
> by async native compilations leveraging the
> `comp-async-report-warnings-errors' customize.
> 
> Is this sufficient to close this bug or do we like to discuss this
> default?

I think we can close this, yes.  Basically, you are saying that most
of these warnings will go away once we get our act together and fix
all the missing 'require's.

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.

> My opinion (got it from the discussion on emacs-devel) is that at least
> for now would be good to keep `comp-async-report-warnings-errors' to t
> for the reason I've explained in the mail I'm quoting.

Agreed.

Thanks.





  parent reply	other threads:[~2021-02-26  7:17 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 [this message]
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
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

  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=83o8g7qovi.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 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).