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: Sat, 01 Apr 2023 18:10:51 +0300 [thread overview]
Message-ID: <83pm8ny6x0.fsf@gnu.org> (raw)
In-Reply-To: <CAF5D8-sFWUdOdFdXgvMmbyzTRf0Y_muFCHhre7B14ofdLRYKow@mail.gmail.com> (message from Yoichi Nakayama on Sat, 1 Apr 2023 23:28:12 +0900)
> From: Yoichi Nakayama <yoichi.nakayama@gmail.com>
> Date: Sat, 1 Apr 2023 23:28:12 +0900
> Cc: emacs-devel@gnu.org
>
> On Sat, Apr 1, 2023 at 10:54 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > I asked why you cannot invoke emacsclient to create a frame, if that
> > will solve your problem? Why do you have to insist on using an
> > existing frame? What am I missing here?
>
> I'm using EDITOR='emacsclient -t'. I don't insist on using an existing frame.
>
> I asked this question because I wanted to avoid putting restrictions
> on the fix I'm proposing to magit. Since emacsclient can either create
> frames or not, I would prefer to have no restrictions in either case.
> If emacsclient's limitation remains that there is no way to get the client's
> environment variables when it doesn't create a frame, I think I'll have to
> accept that my magit fix remains limited.
I'd prefer not to pass environment variables unless a new frame is
being created, yes.
next prev parent reply other threads:[~2023-04-01 15:10 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
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 [this message]
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=83pm8ny6x0.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).