From: Yoichi Nakayama <yoichi.nakayama@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Can emacsclient send environment variables even if it doesn't create a frame?
Date: Sat, 1 Apr 2023 23:54:05 +0900 [thread overview]
Message-ID: <CAF5D8-u=gN+8gDH48fZufmygObZJ4kGT7YBw2+a60oAXffRhhA@mail.gmail.com> (raw)
In-Reply-To: <83ttxzyafp.fsf@gnu.org>
On Sat, Apr 1, 2023 at 10:54 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Yoichi Nakayama <yoichi.nakayama@gmail.com>
> > Date: Sat, 1 Apr 2023 22:37:30 +0900
> > Cc: emacs-devel@gnu.org
> >
> > No, it will not update the frame-parameter of the existing frame.
> > I’ve confirmed
> > (frame-parameter nil 'environment) => nil
> > on the window/buffer created by the modified emacsclient, while
> > (process-get (car server-buffer-clients) 'env)
> > returns environment variables on it.
>
> That's because we currently refrain from changing the 'environment'
> frame parameter -- we tried at some point, and it caused problems we
> decided to defer to later. But it is still an option to do that at
> some point, and so I don't want to block that possibility for trhe
> benefit of this use case.
I understand the situation.
However, I would like there to be a way to propagate the client's
environment variables without updating the frame's environment.
Because users of emacsclient don't necessarily want to affect the
entire frame. The server-buffer-clients element has a 1:1
correspondence with clients, so I think it makes sense to always
store client information there. I find it strange that the
server-buffer-clients element doesn't have environment variables
when we don't create a frame.
--
Yoichi NAKAYAMA
next prev parent reply other threads:[~2023-04-01 14:54 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
2023-04-01 14:54 ` Yoichi Nakayama [this message]
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='CAF5D8-u=gN+8gDH48fZufmygObZJ4kGT7YBw2+a60oAXffRhhA@mail.gmail.com' \
--to=yoichi.nakayama@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).