GNU bug report logs - #47806
28.0.50; `make-frame` frame should probably clone the `environment` parameter into the new frame

Previous Next

Package: emacs;

Reported by: Thibault Polge <thibault <at> thb.lt>

Date: Thu, 15 Apr 2021 18:30:02 UTC

Severity: normal

Tags: moreinfo

Found in version 28.0.50

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Thibault Polge <thibault <at> thb.lt>
Cc: 47806 <at> 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
> From: Thibault Polge <thibault <at> 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?





This bug report was last modified 3 years and 17 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.