From: Eli Zaretskii <eliz@gnu.org>
To: Jerome <an.inbox@free.fr>
Cc: 74157@debbugs.gnu.org
Subject: bug#74157: 30.0.92; `emacsclient-program-name' doesn't factor Emacs name changes
Date: Fri, 01 Nov 2024 16:57:23 +0200 [thread overview]
Message-ID: <864j4r0zos.fsf@gnu.org> (raw)
In-Reply-To: <fe5dddac-b6c3-400c-8004-7d6f887dc09d@free.fr> (message from Jerome on Fri, 1 Nov 2024 16:51:32 +0900)
> Date: Fri, 1 Nov 2024 16:51:32 +0900
> From: Jerome <an.inbox@free.fr>
>
> Emacs 30 adds the `emacsclient-program-name', but its default value
> doesn't factor the build time Emacs name configuration changes (with
> prefix, suffix and sed transormation). I only verified this with the
> suffix confguration, but assume prefix and sed transformation are the
> same.
>
> In my case I configured with `--program-suffix=-30pre'. The Emacs client
> program is, as expected, `emacsclient-30pre', but the value of
> `emacsclient-program-name' is still `'emacsclient'. The variable value
> should reflect the configure time name change(s).
It's actually more complex than that: the programs are renamed only
when Emacs is installed, not when Emacs is built. So when Emacs is
run from the build tree, this variable should have its original name,
and only when Emacs is run from its installed location, the name
should reflect the transform. Which means the name transformation
cannot be static, at build time; it must be done at run time when we
take note of invocation-name.
> This would make `with-editor' simpler (from Emacs 30 onward) as no
> heuristics would be needed to derive the Emacs client name. See:
> https://github.com/magit/with-editor/issues/132
It's too late for Emacs 30 for such non-trivial changes,
unfortunately. So we can only improve this in Emacs 31.
prev parent reply other threads:[~2024-11-01 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 7:51 bug#74157: 30.0.92; `emacsclient-program-name' doesn't factor Emacs name changes Jerome
2024-11-01 14:57 ` Eli Zaretskii [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=864j4r0zos.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74157@debbugs.gnu.org \
--cc=an.inbox@free.fr \
/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.