[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Can emacsclient send environment variables even if it doesn't create
Re: Can emacsclient send environment variables even if it doesn't create a frame?
Sat, 1 Apr 2023 23:54:05 +0900
On Sat, Apr 1, 2023 at 10:54 PM Eli Zaretskii <email@example.com> wrote:
> > From: Yoichi Nakayama <firstname.lastname@example.org>
> > Date: Sat, 1 Apr 2023 22:37:30 +0900
> > Cc: email@example.com
> > 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.