unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 59658@debbugs.gnu.org
Subject: bug#59658: native-compile-prune-cache deletes *.eln files in the build's native-lisp directories
Date: Mon, 28 Nov 2022 16:46:32 +0200	[thread overview]
Message-ID: <83bkornnlj.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0STBJxz0NFrGnQpqoG_PvDWEGO43jaXje6E8Q-ieEMkJMw@mail.gmail.com> (message from Juanma Barranquero on Mon, 28 Nov 2022 15:11:10 +0100)

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Mon, 28 Nov 2022 15:11:10 +0100
> 
> This is on Windows, and running Emacs in-place after building from trunk (no installation).
> 
> If you have several VERSION-xxxxxxxx directories under native-lisp/ and do 
> 
> M-x native-compile-prune-cache <RET>
> 
> this deletes any .eln files in the VERSION-xxxxxxxx directories of the stale caches. Their preloaded/
> subdirectories and content are not affected.
> 
> Presumably this should skip the last entry in native-comp-eln-load-path, which is documented as being
> "assumed to be the system one".

Yes, I think it should skip the last entry.  AFAIR, that was the intent with
this command, in which case what it does now is an oversight of sorts.





  reply	other threads:[~2022-11-28 14:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-28 14:11 bug#59658: native-compile-prune-cache deletes *.eln files in the build's native-lisp directories Juanma Barranquero
2022-11-28 14:46 ` Eli Zaretskii [this message]
2022-11-28 16:49   ` Juanma Barranquero

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=83bkornnlj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=59658@debbugs.gnu.org \
    --cc=lekktu@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).