unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jimmy Wong <wyuenho@gmail.com>
Cc: 63871@debbugs.gnu.org
Subject: bug#63871: 29.0.91; JIT native comp triggered to compile loaddefs repeatedly on require
Date: Sat, 03 Jun 2023 17:17:11 +0300	[thread overview]
Message-ID: <83bkhw8wbc.fsf@gnu.org> (raw)
In-Reply-To: <02a149b3-6081-45f7-ba1e-fc037720e140@Spark> (message from Jimmy Wong on Sat, 3 Jun 2023 15:11:05 +0100)

> Date: Sat, 3 Jun 2023 15:11:05 +0100
> From: Jimmy Wong <wyuenho@gmail.com>
> Cc: 63871@debbugs.gnu.org
> 
> I expect the buffer orders in the buffer list to be restored when desktop mode restores a session, not
> have an async native compile log buffer inserted at the top so I can quickly switch to the second to last
> buffer I was working on before the restart.

This expectation is incorrect.  desktop.el doesn't (and cannot)
promise that no new buffers will be created as part of restoring the
session.

If this gets in the way of some of your workflows, you can easily
write some Lisp for your init file, which will bury this buffer.





  reply	other threads:[~2023-06-03 14:17 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 [this message]
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

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=83bkhw8wbc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=63871@debbugs.gnu.org \
    --cc=wyuenho@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).