unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jimmy Wong <wyuenho@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 63871@debbugs.gnu.org
Subject: bug#63871: 29.0.91; JIT native comp triggered to compile loaddefs repeatedly on require
Date: Sat, 3 Jun 2023 16:11:13 +0100	[thread overview]
Message-ID: <f7cee397-8dc8-4b69-bddc-ec311c0fb457@Spark> (raw)
In-Reply-To: <834jno8u33.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 616 bytes --]

Thanks, I’m aware of that hook. I just always wanted it to be buried whenever it is created. I suspect this perhaps can be put into nativecomp as an enhancement.
On 3 Jun 2023 at 4:04 PM +0100, Eli Zaretskii <eliz@gnu.org>, wrote:
> > Date: Sat, 3 Jun 2023 15:50:37 +0100
> > From: Jimmy Wong <wyuenho@gmail.com>
> > Cc: 63871@debbugs.gnu.org
> >
> > Thanks. I ended up advising get-buffer-create instead as I don’t know how to add a hook to
> > buffer-list-update-hook and not run into an infinite loop.
>
> My suggestion would be to add this function to
> desktop-after-read-hook. Did you try that?

[-- Attachment #2: Type: text/html, Size: 1064 bytes --]

      reply	other threads:[~2023-06-03 15:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-03 13:22 bug#63871: 29.0.91; JIT native comp triggered to compile loaddefs repeatedly on require Jimmy Yuen Ho Wong
2023-06-03 13:51 ` Eli Zaretskii
2023-06-03 13:54   ` Jimmy Wong
2023-06-03 14:09     ` Eli Zaretskii
2023-06-03 14:11       ` Jimmy Wong
2023-06-03 14:17         ` Eli Zaretskii
2023-06-03 14:02   ` Jimmy Wong
2023-06-03 14:11     ` Eli Zaretskii
2023-06-03 14:15       ` Jimmy Wong
2023-06-03 14:25         ` Eli Zaretskii
2023-06-03 14:05   ` Jimmy Wong
2023-06-03 14:14     ` Eli Zaretskii
2023-06-03 14:17       ` Jimmy Wong
2023-06-03 14:26         ` Eli Zaretskii
2023-06-03 14:50           ` Jimmy Wong
2023-06-03 15:05             ` Eli Zaretskii
2023-06-03 15:11               ` Jimmy Wong [this message]

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=f7cee397-8dc8-4b69-bddc-ec311c0fb457@Spark \
    --to=wyuenho@gmail.com \
    --cc=63871@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).