From: "José Manuel García-Patos" <jm.inform@gesaku.es>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs 27.1 - Issue with pdumper
Date: Fri, 28 Aug 2020 09:38:42 +0200 [thread overview]
Message-ID: <20200828073842.GA6136@cervantes.ciudades-secretas.net> (raw)
In-Reply-To: <83y2lzz46h.fsf@gnu.org>
Eli Zaretskii escribió
> That's not my reading of the code. How do you see that Emacs looks
> for emacs.pdmp before looking for BASENAME_OF_EMACS.pdmp? My reading
> of the code is that we do the exact opposite: emacs.pdmp is looked for
> as the last resort.
The way I see it, the current order is:
(1) --dump-file=FILE command-line option
(2) <basename>.pdmp (in the same directory as the executable)
(3) emacs.pdmp (in PATH_EXEC)
(4) <basename>.pdmp in PATH_EXEC
Personally, I don't see the point of (2), but if it's there, I'm sure
there is a reason. My proposal is to swap (3) and (4).
(3') <basename>.pdmp in PATH_EXEC
(4') emacs.pdmp
That's my actual set-up: emacs-no-x11 goes through (3') and regular
emacs goes through (4'). With the current order, emacs.pdmp would be
found in (3), (4) would never be executed and I would get the error I
mentioned when I tried to run emacs-no-x11. Regular emacs would not be
affected either way, because it is the default.
You might say: “You can use (2), too.” Yes, but leaving dump files in
/usr/bin is not as clean a solution as leaving them where they
belong. Even the comment in the code hints at that:
/* Finally, look for basename(argv0)+".pdmp" in PATH_EXEC.
This way, they can rename both the executable and its pdump
file in PATH_EXEC, and have several Emacs configurations in
the same versioned libexec subdirectory. */
All the best.
--
José Manuel García-Patos
Madrid
prev parent reply other threads:[~2020-08-28 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 21:32 Emacs 27.1 - Issue with pdumper José Manuel García-Patos
2020-08-28 6:15 ` Eli Zaretskii
2020-08-28 7:38 ` José Manuel García-Patos [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200828073842.GA6136@cervantes.ciudades-secretas.net \
--to=jm.inform@gesaku.es \
--cc=help-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.