From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Not loading the Registry settings Date: Tue, 15 Sep 2009 09:34:33 -0400 Message-ID: References: <87skerr30v.fsf@catnip.gol.com> 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: ger.gmane.org 1253021698 3916 80.91.229.12 (15 Sep 2009 13:34:58 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 15 Sep 2009 13:34:58 +0000 (UTC) Cc: David De La Harpe Golden , Emacs developers , Miles Bader To: Juanma Barranquero Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Sep 15 15:34:51 2009 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 1MnYBG-000492-86 for ged-emacs-devel@m.gmane.org; Tue, 15 Sep 2009 15:34:50 +0200 Original-Received: from localhost ([127.0.0.1]:41038 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MnYBF-00072j-7I for ged-emacs-devel@m.gmane.org; Tue, 15 Sep 2009 09:34:49 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MnYB9-00072H-O2 for emacs-devel@gnu.org; Tue, 15 Sep 2009 09:34:43 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MnYB4-00071s-5D for emacs-devel@gnu.org; Tue, 15 Sep 2009 09:34:42 -0400 Original-Received: from [199.232.76.173] (port=33374 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MnYB3-00071p-U9 for emacs-devel@gnu.org; Tue, 15 Sep 2009 09:34:37 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:10346 helo=ironport2-out.pppoe.ca) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MnYB1-0007gy-PJ; Tue, 15 Sep 2009 09:34:35 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqIEAKw0r0pFpZBe/2dsb2JhbACBU9xkhBcFh3U X-IronPort-AV: E=Sophos;i="4.44,390,1249272000"; d="scan'208";a="45703814" Original-Received: from 69-165-144-94.dsl.teksavvy.com (HELO ceviche.home) ([69.165.144.94]) by ironport2-out.pppoe.ca with ESMTP; 15 Sep 2009 09:32:52 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id 7BD31B42D1; Tue, 15 Sep 2009 09:34:33 -0400 (EDT) In-Reply-To: (Juanma Barranquero's message of "Tue, 15 Sep 2009 11:26:25 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. 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:115351 Archived-At: >> Thanks. =A0The patch below should address this issue (it just moves code >> around). > After your patch, setting the variable in Lisp works (see code below; > it does not include X changes, only Windows). Good, thanks. > The only drawback is that, on Windows, environment variables (HOME, > SHELL, TERM, LANG, PRELOAD_WINSOCK and a few others) can also be > defined in the registry, and they are loaded in > w32.c:init_environment(), so -Q will not affect them. That is bad, > because it negates one of the advantages of this change, i.e., making > emacs -Q more useful for testing. OTOH, it's just the same behavior as under POSIX where environment variables are not provided via xrm but directly (and -Q does not override them). For HOME settings, I think it's TRT. For other variables, it's less clear, but I think it's OK for now. >> Well, I'm not sure if it would be useful, but the name seems to reflect >> more precisely the effect of the variable, and indeed it can later on >> be changed from Lisp, tho it's not clear whether that would be useful. > BTW, the question of whether "emacs -Q -xrm myresouce" should obey > myresource or not is still open. I think it *should* obey myresource. I don't know how to implement that behavior, tho. Stefan