unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Konstantin Kharlamov <hi-angel@yandex.ru>
Cc: 60854@debbugs.gnu.org
Subject: bug#60854: [PATCH] Make warnings show a "warning" emoji instead of a stop-sign
Date: Fri, 31 Mar 2023 10:05:56 +0300	[thread overview]
Message-ID: <83pm8p2yej.fsf@gnu.org> (raw)
In-Reply-To: <cb90240a14215f63f86c889b435296155cec8f20.camel@yandex.ru> (message from Konstantin Kharlamov on Fri, 31 Mar 2023 09:26:38 +0300)

> From: Konstantin Kharlamov <hi-angel@yandex.ru>
> Cc: 60854@debbugs.gnu.org
> Date: Fri, 31 Mar 2023 09:26:38 +0300
> 
> Actually, scratch that, it's even worse. You see: the byte-compiled
> packages are natively-compiled on demand, i.e. on the first use. So,
> suppose you updated your (M)ELPA packages. What happens is that you
> get a bunch of warnings for packages that were loaded immediately,
> which is not all of them. During Emacs use later, as you open new
> files that weren't opened during the update thus triggering the
> according modes to load, you will get more and more new warnings.

Emacs 28 with native-compilation was released a year ago.  MELPA
packages should have adapted to that long ago, by fixing the problems
which cause those warnings.  My suggestion is to file issues with the
respective developers and pinging them until they resolve this.  In
almost all cases, these warnings are due to missing 'require's or
other similar omissions.  There's no justification for these problems
to exist in the year 2023.





  reply	other threads:[~2023-03-31  7:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-11  8:45 bug#61413: [PATCH] Make warnings show a "warning" emoji instead of a stop-sign Konstantin Kharlamov
     [not found] ` <handler.61413.B.16761051946467.ack@debbugs.gnu.org>
2023-02-11  8:49   ` bug#61413: Acknowledgement ([PATCH] Make warnings show a "warning" emoji instead of a stop-sign) Konstantin Kharlamov
2023-02-11 10:36 ` bug#61413: [PATCH] Make warnings show a "warning" emoji instead of a stop-sign Eli Zaretskii
2023-02-11 10:56   ` bug#60854: " Konstantin Kharlamov
2023-03-30 20:58     ` bug#60854: " Konstantin Kharlamov
2023-03-31  5:55       ` Eli Zaretskii
2023-03-31  6:19         ` Konstantin Kharlamov
2023-03-31  6:26           ` Konstantin Kharlamov
2023-03-31  7:05             ` Eli Zaretskii [this message]
2023-03-31  7:48               ` Konstantin Kharlamov
2023-03-31  7:54                 ` Eli Zaretskii
2023-03-31  8:10                   ` Konstantin Kharlamov
2023-03-31  7:00           ` 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=83pm8p2yej.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=60854@debbugs.gnu.org \
    --cc=hi-angel@yandex.ru \
    /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).