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: Thu, 14 Jun 2007 10:57:33 +0200 Message-ID: <864pla7w1u.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> 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 1181811467 30694 80.91.229.12 (14 Jun 2007 08:57:47 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 14 Jun 2007 08:57:47 +0000 (UTC) Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca, Jason Rumney To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jun 14 10:57:45 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 1Hyl9C-0007Xn-Ct for ged-emacs-devel@m.gmane.org; Thu, 14 Jun 2007 10:57:42 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hyl9B-0000AM-Q1 for ged-emacs-devel@m.gmane.org; Thu, 14 Jun 2007 04:57:41 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Hyl97-0000AH-5I for emacs-devel@gnu.org; Thu, 14 Jun 2007 04:57:37 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Hyl96-0000A5-HU for emacs-devel@gnu.org; Thu, 14 Jun 2007 04:57:36 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hyl96-0000A2-8Z for emacs-devel@gnu.org; Thu, 14 Jun 2007 04:57:36 -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 1Hyl95-0002uY-Hi for emacs-devel@gnu.org; Thu, 14 Jun 2007 04:57:35 -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 KAA16537 for ; Thu, 14 Jun 2007 10:57:32 +0200 X-Delivered-To: Original-Received: (qmail 27103 invoked from network); 14 Jun 2007 08:57:33 -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 ; 14 Jun 2007 08:57:33 -0000 Original-Received: by lola.quinscape.zz (Postfix, from userid 1001) id D213DF9F60; Thu, 14 Jun 2007 10:57:33 +0200 (CEST) In-Reply-To: (Richard Stallman's message of "Thu\, 14 Jun 2007 03\:49\:12 -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:72850 Archived-At: Richard Stallman writes: > What do people think of this idea: make call-process and > start-process supply the values of the envvars TERM and DISPLAY from > two variables, term-environment-variable and > display-environment-variable, if they are not specified in > process-environment. 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. One could also put everything into one terminal-local "terminal-process-environment" which would be effectively prepended to process-environment. I'd prefer that approach, and it would mostly work in _my_ preferred modus operandi. However, see below: > This way, Lisp programs that bind TERM explicitly will work right. > However, in the future they could bind term-environment-variable and > display-environment-variable, instead of fussing with > process-environment. > > Would someone like to check whether this gives good results all > around, for the Lisp code that operates on the environment? 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. 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. So this scheme, while definitely cleaner than the shared-tail approach, would not be backward-compatible to a large body of existing code _if_ people tried to make the bulk of their environment terminal-local. The effects would be somewhat ameliorated by only putting environment variables which _differ_ from the global setting into terminal-process-environment, but it would be still quite a nuisance. --=20 David Kastrup