GNU bug report logs - #77502
31.0.50; Should after-load-functions hook report .eln file names?

Previous Next

Full log

Message #19 received at 77502-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Sean Devlin <spd <at> toadstyle.org>
Cc: acorallo <at> gnu.org, monnier <at> iro.umontreal.ca, 77502-done <at> debbugs.gnu.org
Subject: Re: bug#77502: 31.0.50;
 Should after-load-functions hook report .eln file names?
Date: Sat, 19 Apr 2025 16:54:13 +0300

> From: Sean Devlin <spd <at> toadstyle.org>
> Date: Sat, 5 Apr 2025 11:31:19 -0500
> Cc: Eli Zaretskii <eliz <at> gnu.org>, Andrea Corallo <acorallo <at> gnu.org>,
>  77502 <at> debbugs.gnu.org
> 
> Hi folks,
> 
> > On Apr 5, 2025, at 10:07 AM, Stefan Monnier <monnier <at> iro.umontreal.ca> wrote:
> > 
> > 
> >> 
> >> Not sure if this is a bug or a feature.  We record the *.elc names in
> >> load-history, and those are the names passed to after-load-functions.
> >> I've added Stefan and Andrea to this discussion, in case they have
> >> comments.
> > 
> > It was done on purpose, at least for backward compatibility reasons, but
> > also because it's easier to find the `.eln` from the `.elc` than
> > the reverse.
> 
> I see, thanks.
> 
> In my case, I don’t necessarily even care about getting the .eln paths in the after-load-functions hook. I just got confused by the results and thought maybe my native loader was not working correctly due to some misconfiguration on my end. In other words, I have no problem with the current behavior, but I do think maybe we should update the documentation somewhere to describe how the hook behaves when the native loader is enabled.
> 
> Cheers.

No further comments, so I'm now closing this bug.

Previous Next

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