From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kevin Rodgers Newsgroups: gmane.emacs.help Subject: Re: GNU emacs locks files modified with CVS Date: Thu, 18 Dec 2003 10:19:55 -0700 Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: <3FE1E1BB.6050108@yahoo.com> References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1071768858 14903 80.91.224.253 (18 Dec 2003 17:34:18 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 18 Dec 2003 17:34:18 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Dec 18 18:34:13 2003 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AX22P-00066Q-00 for ; Thu, 18 Dec 2003 18:34:13 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AX2xL-000454-Bt for geh-help-gnu-emacs@m.gmane.org; Thu, 18 Dec 2003 13:33:03 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!syros.belnet.be!news.belnet.be!news2.euro.net!newshub1.home.nl!home.nl!borium.box.nl!fu-berlin.de!uni-berlin.de!170.207.51.80!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 39 Original-NNTP-Posting-Host: 170.207.51.80 Original-X-Trace: news.uni-berlin.de 1071767985 7293447 170.207.51.80 ([82742]) User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:0.9.4.1) Gecko/20020406 Netscape6/6.2.2 X-Accept-Language: en-us Original-Xref: shelby.stanford.edu gnu.emacs.help:119483 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.help:15424 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:15424 Maurizio Loreti wrote: > gebser@speakeasy.net writes: > > >>Because it would take a lot of thinking to hash out which is the correct >>file to put this in, whether the DISPLAY is a resource or not, whether >>this variable should be set for all interactive shells or just for >>logins, and because I don't wish to argue any of this, I'll just say >>that I disagree and believe that .bashrc *is* the proper place for >>setting DISPLAY. As said at the outset, everyone can set up their >>systems however they wish. >> > > You are free to do a lot of things - to shoot yourself in a foot, if > you like. I dare to dissent. From 'man bash': > > ,----- > | When bash is invoked as an interactive login shell ... it first reads > | and executes commands from the file /etc/profile, if that file exists. > | After reading that file, it looks for ~/.bash_profile, ~/.bash_login, > | and ~/.profile, in that order, and reads and executes commands from > | the first one that exists and is readable. > | ... > | When an interactive shell that is not a login shell is started, bash > | reads and executes commands from ~/.bashrc, if that file exists. > `----- > > Since all non-login shells (used e.g. to run commands in a subshell) > inherit the environment from the common ancestor, the login shell, I > think it is just a loss of time to recompute every time an environment > variable that *cannot* have been changed. YMMV, of course. Right. So ~/.bash_profile, ~/.bash_login, or ~/.profile is the right place to set DISPLAY. -- Kevin Rodgers