all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 44746@debbugs.gnu.org, akrl@sdf.org
Subject: bug#44746: 28.0.50; [feature/native-comp] Noisy "*Warnings*" buffer shown on start
Date: Fri, 26 Feb 2021 09:19:39 +0200	[thread overview]
Message-ID: <83mtvrqos4.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmMi2QvNsrMROk5CWfTRfryU-Z8ssUW0jbYbqB6h41Obw@mail.gmail.com> (message from Stefan Kangas on Thu, 25 Feb 2021 17:59:18 -0600)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Thu, 25 Feb 2021 17:59:18 -0600
> 
> The above reasoning is correct and valid for any ELisp package, I think.
> 
> But most of the warnings I see are actually from my init files.  There,
> I specifically do not want to `require' everything I need as that would
> slow down startup.  It also places undue burden on mere users that want
> to customize this or that option from their init file.

But you could bind that variable to nil when loading those init files,
right?





  reply	other threads:[~2021-02-26  7:19 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 [this message]
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
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=83mtvrqos4.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.