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 07:42:36 +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: <3FDF1C0E.50106@tpd.tno.nl> 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 1071645464 30831 80.91.224.253 (17 Dec 2003 07:17:44 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 17 Dec 2003 07:17:44 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Dec 17 08:17:41 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 1AWVwD-00044b-00 for ; Wed, 17 Dec 2003 08:17:41 +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 1AWWqX-0007Cz-25 for geh-help-gnu-emacs@m.gmane.org; Wed, 17 Dec 2003 03:15:53 -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: 71 Original-NNTP-Posting-Host: mlinux.pd.infn.it Original-X-Trace: sunnews.cern.ch 1071643356 17098 (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:15353 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:15353 Pepijn Kenter writes: > gebser@speakeasy.net wrote: > > There's two ways which will keep/set the DISPLAY variable: > > First, if the DISPLAY variable is set in user1 and you do "su > > user2", then the environment of user1 will carry into user2. IOW, > > you're good. Second, if you, instead, do "su - user2", then you will > > have a fresh environment, that of user2. If user2's environment > > doesn't have the DISPLAY variable set properly, you can do this by > > setting this in user2's ~/.bashrc file... if user2's default shell > > is bash-- if you're using some other shell, consult the manpage for > > the proper file and command syntax for setting the environment. > > > Thanks for your reply but the .bashrc seems to me the wrong place to > set the DISPLAY variable. > If you login from another machine it won't be set properly. Correct. The right place is .bash_profile, executed at login. FWIW, this is from my own .bash_profile: ,----- | # Tries to figure out a correct DISPLAY environment variable | | if [ -n "$DISPLAY" ] | then | # if DISPLAY is set, we assume it is also valid; if it is not, | # the user may always change it later ($DISPLAY is printed at | # the end of the login procedure). | | REMOTE="${DISPLAY%%:*}" | else | temp0=$(who am i | awk '{print $2}') | | if [ "$temp0" = "console" ] | then | REMOTE="localhost" | DISPLAY=":0.0" | else | temp1=$(who --lookup | grep "$temp0 " | uniq | awk '{print $6}') | # Note the blank-------------------^ | if [ -n "$temp1" ] | then | temp2=$(echo $temp1 | sed -e 's/(//' -e 's/)//') | temp3=$(echo $temp2 | cut -d. -f2) | if [ "$temp3" = "pd" ] | then | # If on host.pd.infn.it, DISPLAY="host:0.0"; | # if not, DISPLAY="host.dom.ain:0.0" | REMOTE=$(echo $temp2 | cut -d. -f1) | else | REMOTE="${temp2%%:*}" | fi | DISPLAY="${REMOTE}:0.0" | unset temp2 temp3 | else | REMOTE="" | DISPLAY=":0.0" | fi | unset temp1 | fi | unset temp0 | fi | | export REMOTE DISPLAY | echo "DISPLAY is now: $DISPLAY" `----- -- Maurizio Loreti http://www.pd.infn.it/~loreti/mlo.html Dept. of Physics, Univ. of Padova, Italy ROT13: ybergv@cq.vasa.vg