GNU bug report logs - #79124
emacs -Q doesn't give me a clean slate

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: rpluim <at> gmail.com, 79124 <at> debbugs.gnu.org, rms <at> gnu.org
Subject: bug#79124: emacs -Q doesn't give me a clean slate
Date: Wed, 06 Aug 2025 21:59:49 +0300

> Date: Wed, 6 Aug 2025 09:29:44 -0700
> Cc: rpluim <at> gmail.com, rms <at> gnu.org, 79124 <at> debbugs.gnu.org
> From: Paul Eggert <eggert <at> cs.ucla.edu>
> 
> On 2025-08-06 09:22, Eli Zaretskii wrote:
> 
> > Because startup.el can load Lisp packages that are not preloaded.  The
> > terminal-specific library from lisp/term/ and warnings.el are two that
> > come to mind, but I won't be surprised that there are more.
> 
> That's fine; these files can be compiled as needed. Emacs simply need 
> not consult the user home directory to see whether they have already 
> been compiled by a previous Emacs execution.

It currently can't, and I'm unwilling to complicate what we have so it
will be able to, sorry.

> > I fail to see the difference between trusting files in /tmp and
> > trusting files in ~/.emacs.d/eln-cache.
> 
> Those files in /tmp are all created by the current Emacs execution, and 
> can be trusted for that reason. The files that were already in 
> ~/.emacs.d/eln-cache are not, and they might have been corrupted for 
> various reasons since they were created by a previous execution. That's 
> an important difference.

I fail to see the important difference: who said the corruption, such
as it is, could only happen some time ago, but not immediately as the
files are created?

But this discussion leads nowhere, since we both have opinions that
cannot be changed by these arguments.  So let's leave it at that.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.