From: Eli Zaretskii <eliz@gnu.org>
To: rswgnu@gmail.com, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 55305@debbugs.gnu.org
Subject: bug#55305: 28.0.50: With async nativecomp, package manager fails to load hyperbole-autoloads.el before compilation
Date: Sun, 15 May 2022 08:15:00 +0300 [thread overview]
Message-ID: <8335hbl6ln.fsf@gnu.org> (raw)
In-Reply-To: <CA+OMD9huRvs+jBVHF4uLjC=prapVhfPQNriMSKO8YvvqG1YiVQ@mail.gmail.com> (message from Robert Weiner on Sat, 14 May 2022 18:40:03 -0400)
> From: Robert Weiner <rsw@gnu.org>
> Date: Sat, 14 May 2022 18:40:03 -0400
> Cc: 55305@debbugs.gnu.org
>
> On Sat, May 14, 2022 at 11:05 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
> If you are lobbying for having more automated discovery and loading of
> loaddefs files, then you are asking for a new feature, not reporting a
> bug in Emacs 28 that didn't exist in previous versions. And I don't
> think I agree that this feature is a good idea, for when a file is
> compiled. But we could discuss this feature request; my point is that
> there's no bug here, but a normal behavior we have with any
> compilation of any Lisp file in any Emacs version.
>
> Hi Eli:
>
> I see what you are saying. I wish Stefan would say
> something here too with his perspective of dealing
> with autoload files in Elpa packages.
Stefan doesn't read this list. I've CC'ed him now, so he could
comment.
next prev parent reply other threads:[~2022-05-15 5:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 20:05 bug#55305: 28.0.50: With async nativecomp, package manager fails to load hyperbole-autoloads.el before compilation Robert Weiner
2022-05-08 5:09 ` Eli Zaretskii
2022-05-12 5:14 ` Robert Weiner
2022-05-12 5:51 ` Eli Zaretskii
2022-05-12 6:21 ` Robert Weiner
2022-05-12 7:22 ` Eli Zaretskii
2022-05-14 14:47 ` Robert Weiner
2022-05-14 15:05 ` Eli Zaretskii
2022-05-14 22:40 ` Robert Weiner
2022-05-15 5:15 ` Eli Zaretskii [this message]
2022-05-15 15:59 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-15 16:17 ` Eli Zaretskii
2022-05-15 16:22 ` Eli Zaretskii
2022-05-15 16:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-15 17:01 ` Eli Zaretskii
2022-05-15 17:15 ` Eli Zaretskii
2022-05-15 20:12 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-16 2:31 ` Eli Zaretskii
2022-05-16 16:40 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-16 16:57 ` Eli Zaretskii
2022-05-16 17:17 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-15 20:39 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-16 2:33 ` Eli Zaretskii
2022-05-16 9:34 ` Andrea Corallo
2022-05-16 16:42 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-16 16:59 ` Eli Zaretskii
2022-05-16 22:27 ` Robert Weiner
2022-05-17 2:27 ` Eli Zaretskii
2023-06-07 21:36 ` Andrea Corallo
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=8335hbl6ln.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=55305@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rswgnu@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).