From: Eli Zaretskii <eliz@gnu.org>
To: Yoichi Nakayama <yoichi.nakayama@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Can emacsclient send environment variables even if it doesn't create a frame?
Date: Wed, 29 Mar 2023 18:46:51 +0300 [thread overview]
Message-ID: <83bkkb7e6s.fsf@gnu.org> (raw)
In-Reply-To: <CAF5D8-sTbKPC4mYkYA0e5sFf+14Wo-GEQFUwus-+6YzJ7aFP7w@mail.gmail.com> (message from Yoichi Nakayama on Wed, 29 Mar 2023 22:45:09 +0900)
> From: Yoichi Nakayama <yoichi.nakayama@gmail.com>
> Date: Wed, 29 Mar 2023 22:45:09 +0900
>
> Currently, emacsclient sends environment variables to the server process only
> if it is going to create a frame. So it is impossible to refer to environment
> variables when calling EDITOR=emacsclient from other programs.
> In contrast, if EDITOR="emacsclient -t" or EDITOR="emacsclient -c" (that is,
> emacsclient creates new frames), you can refer emacsclient's environment
> variables via server-buffer-clients.
>
> Is it possible to eliminate the following conditional branching by create_frame
> in lib-src/emacsclient.c?
That would mean a single frame could "inherit" environment variables
from different shells, which will be at least confusing, if not
contradictory. For example, what about environment variables like
PATH?
> Use case:
> Refer GIT_INDEX_FILE to show correct diff even when emacsclient is invoked
> by `git commit -a` or `git commit filename` (where GIT_INDEX_FILE points to
> a temporary index file), along with the commit message edit buffer.
Why cannot you call emacsclient in that case with -t or -c option?
AFAIR, Git can use a Git-special variable GIT_EDITOR, so you could
define that to create a new frame without affecting the more general
EDITOR setting.
next prev parent reply other threads:[~2023-03-29 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 13:45 Can emacsclient send environment variables even if it doesn't create a frame? Yoichi Nakayama
2023-03-29 15:46 ` Eli Zaretskii [this message]
2023-04-01 13:37 ` Yoichi Nakayama
2023-04-01 13:54 ` Eli Zaretskii
2023-04-01 14:28 ` Yoichi Nakayama
2023-04-01 15:10 ` Eli Zaretskii
2023-04-01 14:54 ` Yoichi Nakayama
2023-04-01 15:40 ` 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
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=83bkkb7e6s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=yoichi.nakayama@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).