From: "Alex Bennée" <alex.bennee@linaro.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: emacs-devel@gnu.org
Subject: Re: Changes to autoload handling in native-comp branch?
Date: Tue, 14 Apr 2020 23:14:01 +0100 [thread overview]
Message-ID: <87eesphg0m.fsf@linaro.org> (raw)
In-Reply-To: <xjfeesquecd.fsf@sdf.org>
Andrea Corallo <akrl@sdf.org> writes:
> Alex Bennée <alex.bennee@linaro.org> writes:
>
>> Yeah manually running that gives me the same error. It all comes down to
>> the line (file-name-directory #$) which I guess should have some special
>> handling. The weird thing is on my "normal" emacs (GNU Emacs 25.2.2
>> (x86_64-pc-linux-gnu) of 2017-09-22, modified by Debian) executing this
>> line also gives the same error although the *Messages* shows no such
>> problems during load up.
>>
>> Does this indicate there us some sort of special context in the way the
>> autoload code is run? Is file-name-handler-alist modified during
>> autoload processing in a way that isn't picked up by native code?
>
> Hi Alex,
>
> I confirm was bug#40620 and should be fixed by now. The bug was
> introduced by 6e09597e27. '$' is replaced by the reader with
> `load-file-name' value (and in this branch ATM by load-true-file-name).
> This last one I managed to forget to set it were should have been.
>
> Generally speaking I'm not sure having `load-true-file-name' and
> `load-file-name' is the nicest design but this was motivated by
> bug#40099 (glab :)
>
> https://lists.gnu.org/archive/html/bug-gnu-emacs/2020-04/msg00211.html
I've updated my tree and can confirm the bug is now gone and things are
working as normal again.
>
> Bests
>
> Andrea
--
Alex Bennée
next prev parent reply other threads:[~2020-04-14 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 9:57 Changes to autoload handling in native-comp branch? Alex Bennée
2020-04-14 10:14 ` Andrea Corallo
2020-04-14 13:31 ` Alex Bennée
2020-04-14 18:11 ` Andrea Corallo
2020-04-14 22:14 ` Alex Bennée [this message]
2020-04-14 11:19 ` Andrea Corallo
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=87eesphg0m.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=akrl@sdf.org \
--cc=emacs-devel@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).