From: Eli Zaretskii <eliz@gnu.org>
To: Ship Mints <shipmints@gmail.com>
Cc: luangruo@yahoo.com, sbaugh@janestreet.com, larsi@gnus.org,
acorallo@gnu.org, 73318@debbugs.gnu.org
Subject: bug#73318: 31.0.50; with-native-compilation=aot breaks exec -a emacs
Date: Thu, 19 Sep 2024 18:45:29 +0300 [thread overview]
Message-ID: <86o74j8x5y.fsf@gnu.org> (raw)
In-Reply-To: <CAN+1HbreU9wOK+dRCo1sxsmU6BZ-zE5nwzth+xy9zPW2L8Uizg@mail.gmail.com> (message from Ship Mints on Thu, 19 Sep 2024 09:51:44 -0400)
> From: Ship Mints <shipmints@gmail.com>
> Date: Thu, 19 Sep 2024 09:51:44 -0400
> Cc: Eli Zaretskii <eliz@gnu.org>, Spencer Baugh <sbaugh@janestreet.com>, 73318@debbugs.gnu.org,
> larsi@gnus.org, acorallo@gnu.org
>
> I see. It pays, then, to disambiguate between a Linux "system" (which is the typical Emacs case) and Linux
> O/S-based, essentially embedded, environments. In the "system" case, /proc/self/exe should be the
> recommended method, I'd think. In embedded cases, whatever is appropriate in those environments is what
> should be used.
Please re-read what I wrote about the use cases we have to support and
the discussion to which I pointed. No single method can support all
the situations which Emacs needs to support. So there's no "the
recommended method": even if we add /proc/self/exe, it can only be one
of the methods we use to find where the *.eln files are, and not
necessarily the most important one.
next prev parent reply other threads:[~2024-09-19 15:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 15:18 bug#73318: 31.0.50; with-native-compilation=aot breaks exec -a emacs Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-17 15:40 ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-17 17:47 ` Eli Zaretskii
2024-09-17 18:14 ` Ship Mints
2024-09-17 19:07 ` Eli Zaretskii
2024-09-17 19:22 ` Ship Mints
2024-09-17 19:31 ` Eli Zaretskii
2024-09-17 22:31 ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-17 22:45 ` Ship Mints
2024-09-18 13:11 ` Eli Zaretskii
2024-09-19 3:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-19 12:54 ` Ship Mints
2024-09-19 13:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-19 13:51 ` Ship Mints
2024-09-19 15:45 ` Eli Zaretskii [this message]
2024-10-04 12:09 ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-04 12:51 ` Eli Zaretskii
2024-10-04 13:22 ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-04 13:57 ` Eli Zaretskii
2024-10-04 14:02 ` shipmints
2024-10-04 16:51 ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-04 19:09 ` Eli Zaretskii
2024-10-07 14:18 ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-07 18:44 ` Eli Zaretskii
2024-10-07 20:16 ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-08 11:47 ` Eli Zaretskii
2024-10-08 12:16 ` Eli Zaretskii
2024-10-04 19:16 ` Eli Zaretskii
2024-10-08 23:35 ` Stefan Kangas
2024-10-09 12:13 ` 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=86o74j8x5y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=73318@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=sbaugh@janestreet.com \
--cc=shipmints@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.