From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Maurizio Loreti Newsgroups: gmane.emacs.help Subject: Re: GNU emacs locks files modified with CVS Date: 17 Dec 2003 18:54:00 +0100 Organization: I.N.F.N. Padova - CDF/CMS cluster Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: References: Reply-To: mlo@foobar.it NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1071685287 19959 80.91.224.253 (17 Dec 2003 18:21:27 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 17 Dec 2003 18:21:27 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Dec 17 19:21:22 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 1AWgIU-0006wu-00 for ; Wed, 17 Dec 2003 19:21:22 +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 1AWhFt-0000an-Ki for geh-help-gnu-emacs@m.gmane.org; Wed, 17 Dec 2003 14:22:45 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!irazu.switch.ch!switch.ch!cern.ch!news Original-Newsgroups: gnu.emacs.help Original-Lines: 32 Original-NNTP-Posting-Host: mlinux.pd.infn.it Original-X-Trace: sunnews.cern.ch 1071683639 13612 (None) 193.205.157.46 Original-X-Complaints-To: news@sunnews.cern.ch X-Face: #+pXzVo/v'Z(+~kXSsQy'!yT^.5/Zd"g1C|\^eBH(Xy:oJD^,u|/) 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:15378 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:15378 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. -- Maurizio Loreti http://www.pd.infn.it/~loreti/mlo.html Dept. of Physics, Univ. of Padova, Italy ROT13: ybergv@cq.vasa.vg