From: Ken Brown <kbrown@cornell.edu>
To: Bhavin Gandhi <bhavin7392@gmail.com>, 52488@debbugs.gnu.org
Subject: bug#52488: Try basename of agrv0's realpath for .pdmp lookup in libexecdir
Date: Tue, 14 Dec 2021 14:32:24 -0500 [thread overview]
Message-ID: <29de49f6-a57a-fdbd-bba1-17ff74a49f5f@cornell.edu> (raw)
In-Reply-To: <CAOn=hbcpRgtyq3j3oxDZo5Y0+akNUBfHdyX8O+=ECPBp7U0wbw@mail.gmail.com>
On 12/14/2021 2:01 PM, Bhavin Gandhi wrote:
> As the comment from load_pdump_find_executable explains, there are
> setups where the /usr/bin/emacs is a symlink managed by something like
> alternatives. This symlink eventually points to an Emacs binary like
> emacs-28.0.90. These kind of setups are used to have installation of
> multiple versions of Emacs on the same system.
This is exactly the setup that I use on Cygwin, as I alluded to in my message to
the other bug report. But I didn't mention there that I use symlinks managed by
alternatives.
> Supporting resolution of these symlinks while searching for a .pdmp file
> will make it possible to put the .pdmp files in libexecdir instead of
> putting those in the /usr/bin/. I think this should be in addition to
> the possibilities tried currently.
Yes. It's precisely because the symlinks aren't resolved that I've been putting
the .pdmp files in /usr/bin, alongside the emacs executables.
Ken
next prev parent reply other threads:[~2021-12-14 19:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 19:01 bug#52488: Try basename of agrv0's realpath for .pdmp lookup in libexecdir Bhavin Gandhi
2021-12-14 19:25 ` Bhavin Gandhi
2021-12-14 19:32 ` Ken Brown [this message]
2021-12-15 17:56 ` Ken Brown
2021-12-15 18:19 ` Glenn Morris
2021-12-15 18:53 ` Ken Brown
2021-12-15 22:08 ` Ken Brown
2021-12-19 12:57 ` Lars Ingebrigtsen
2021-12-19 15:26 ` Ken Brown
2021-12-23 13:48 ` Ken Brown
2021-12-23 13:50 ` Bhavin Gandhi
2021-12-15 18:24 ` Bhavin Gandhi
2021-12-15 19:32 ` Eli Zaretskii
2021-12-14 19:42 ` Eli Zaretskii
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=29de49f6-a57a-fdbd-bba1-17ff74a49f5f@cornell.edu \
--to=kbrown@cornell.edu \
--cc=52488@debbugs.gnu.org \
--cc=bhavin7392@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 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.