From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Post-22.1 development? Date: Fri, 15 Jun 2007 11:02:23 +0200 Message-ID: <86odjh380w.fsf@lola.quinscape.zz> References: <878xb05ras.fsf@stupidchicken.com> <200706101559.l5AFxBFb006829@oogie-boogie.ics.uci.edu> <86fy4yg62v.fsf@lola.quinscape.zz> <466ED07F.9000002@gnu.org> <864pla7w1u.fsf@lola.quinscape.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1181898160 16285 80.91.229.12 (15 Jun 2007 09:02:40 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 15 Jun 2007 09:02:40 +0000 (UTC) Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca, jasonr@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jun 15 11:02:38 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Hz7hT-0003XK-CG for ged-emacs-devel@m.gmane.org; Fri, 15 Jun 2007 11:02:35 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hz7hS-0002xl-MW for ged-emacs-devel@m.gmane.org; Fri, 15 Jun 2007 05:02:34 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Hz7hN-0002uz-I1 for emacs-devel@gnu.org; Fri, 15 Jun 2007 05:02:29 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Hz7hK-0002sp-Uf for emacs-devel@gnu.org; Fri, 15 Jun 2007 05:02:28 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hz7hJ-0002sY-Hy for emacs-devel@gnu.org; Fri, 15 Jun 2007 05:02:26 -0400 Original-Received: from pc3.berlin.powerweb.de ([62.67.228.11]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Hz7hI-0003KK-Kd for emacs-devel@gnu.org; Fri, 15 Jun 2007 05:02:25 -0400 Original-Received: from quinscape.de (dslnet.212-29-44.ip210.dokom.de [212.29.44.210] (may be forged)) by pc3.berlin.powerweb.de (8.9.3p3/8.9.3) with ESMTP id LAA20311 for ; Fri, 15 Jun 2007 11:02:21 +0200 X-Delivered-To: Original-Received: (qmail 27176 invoked from network); 15 Jun 2007 09:02:23 -0000 Original-Received: from unknown (HELO lola.quinscape.zz) ([10.0.3.43]) (envelope-sender ) by ns.quinscape.de (qmail-ldap-1.03) with SMTP for ; 15 Jun 2007 09:02:23 -0000 Original-Received: by lola.quinscape.zz (Postfix, from userid 1001) id 6D82C8FC76; Fri, 15 Jun 2007 11:02:23 +0200 (CEST) In-Reply-To: (Richard Stallman's message of "Fri\, 15 Jun 2007 04\:48\:28 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/23.0.51 (gnu/linux) X-detected-kernel: Linux 2.4-2.6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:72938 Archived-At: Richard Stallman writes: > These two variables would normally be > > frame-local, and in each frame, they would have the right values for > > that frame's terminal. > > I'd make them terminal-local. > > Either one. > > The problem I see with this is that K=E1roly expressed a strong > preference for having the _complete_ environment terminal-local > (personally, I think this a bad idea but have not been able to > convince him and several others): he preferred to consider a > separately started emacsclient session to have an _independent_ > complete set of environment variables. > > If we want that, it can be a separate and independent feature. > There is no need to combine that question with this one. > It is clear that TERM and DISPLAY should go with the terminal > regardless of use of emacsclient. > > Using the above scheme with terminal-process-environment would still > facilitate that, but in that case most of the direct manipulations and > queries working on process-environment would fail to work. > > `terminal-process-environment' is cumbersome. I'd rather have > `term-environment-variable' and `display-environment-variable', > as I explained. > > This may require rewriting various Lisp programs -- but it brings a > benefit in clarity that can justify an incompatible change. I think it would be confusing if setenv and most particularly getenv did not work for TERM and DISPLAY variables, and I see no particular benefit to letting them stop to work mostly as previously. If setenv/getenv are to remain the preferred accessors, it seems reasonable to gather the terminal-local variables in a single list in order not to have to special-case every variable. --=20 David Kastrup