From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Andreas Fuchs <asf@boinkor.net>
Cc: 43137@debbugs.gnu.org, Vibhav Pant <vibhavp@gmail.com>
Subject: bug#43137: 28.0.50; [feature/native-comp] .eln path fixup confused using relative paths
Date: Wed, 02 Sep 2020 07:28:49 +0000 [thread overview]
Message-ID: <xjf4kogvdqm.fsf@sdf.org> (raw)
In-Reply-To: <CAOHxn7wzbGuKD1bUmXiBuBYjfR_hOoWMFcqMbmhGmkyi3tHO0g@mail.gmail.com> (Andreas Fuchs's message of "Tue, 1 Sep 2020 20:51:43 -0400")
Andreas Fuchs <asf@boinkor.net> writes:
> I think I found the solution: set_invocation_vars requires Vexec_path
> to be initialized correctly, via init_callproc_1. Somehow, mine ends
> up being something other than $PATH. If I set init_callproc_1 up with
> a double_run_guard the same way set_invocation_var is and call it
> from pdumper_load, it results in a correctly-set Vexec_path variable
> and a correctly-set Vinvocation_directory, as well.
> This is really curious, but I guess it would explain why
> the invocation directory variable is empty! What it doesn't explain
> is, why does this work for you? Maybe your $PATH variable is set up
> differently? (Though I don't see where exec-path would be set
> otherwise...)
I guess is beacuse argv0 is not set on macos so raw_name is empty.
Vexec_path comes into play only in this case.
Andrea
prev parent reply other threads:[~2020-09-02 7:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 15:11 bug#43137: 28.0.50; [feature/native-comp] .eln path fixup confused using relative paths Andreas Fuchs
2020-08-31 16:32 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-01 14:15 ` Andreas Fuchs
2020-09-01 19:32 ` Andreas Fuchs
2020-09-01 19:51 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-02 0:51 ` Andreas Fuchs
2020-09-02 4:41 ` Andreas Fuchs
2020-09-02 7:40 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-02 13:49 ` Andreas Fuchs
2020-09-26 13:51 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-02 7:59 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-02 7:28 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=xjf4kogvdqm.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=43137@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=asf@boinkor.net \
--cc=vibhavp@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).