From: Eli Zaretskii <eliz@gnu.org>
To: Thibault Polge <thibault@thb.lt>
Cc: 47806@debbugs.gnu.org
Subject: bug#47806: 28.0.50; `make-frame` frame should probably clone the `environment` parameter into the new frame
Date: Thu, 15 Apr 2021 22:08:38 +0300 [thread overview]
Message-ID: <838s5jxt55.fsf@gnu.org> (raw)
In-Reply-To: <87k0p39zbo.fsf@thb.lt> (message from Thibault Polge on Thu, 15 Apr 2021 20:28:59 +0200)
> From: Thibault Polge <thibault@thb.lt>
> Date: Thu, 15 Apr 2021 20:28:59 +0200
>
> Frames created by `emacsclient` get a copy of the caller's environment
> variables in the `environment` frame property. But frames created from
> other frames (with C-x 5 2, `make-frame`, `make-frame-command`, and so
> on) don't get a copy of those variables (they don't have an
> `environment` frame parameter at all). I believe they should.
How do we know whether a particular frame should or shouldn't have the
'environment' frame parameter? When the frame is created by the
server on behalf of a client, we know. But for a random
frame-creation function, how do we know?
> My use case is talking to the WM, and without this parameter I believe
> it's impossible to distinguish between, eg, frames managed by different
> X servers on the same daemon.
Doesn't the 'display' parameter fit the bill?
next prev parent reply other threads:[~2021-04-15 19:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 18:28 bug#47806: 28.0.50; `make-frame` frame should probably clone the `environment` parameter into the new frame Thibault Polge
2021-04-15 19:08 ` Eli Zaretskii [this message]
2021-04-15 19:47 ` Thibault Polge
2021-04-15 19:54 ` Eli Zaretskii
2021-04-15 22:27 ` Thibault Polge
2021-04-16 6:05 ` Eli Zaretskii
2022-06-29 11:10 ` Lars Ingebrigtsen
2022-06-29 11:15 ` Thibault Polge
2022-06-29 11:29 ` Lars Ingebrigtsen
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=838s5jxt55.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47806@debbugs.gnu.org \
--cc=thibault@thb.lt \
/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).