unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Maurizio Loreti <mlo@foobar.it>
Subject: Re: GNU emacs locks files modified with CVS
Date: 17 Dec 2003 18:54:00 +0100	[thread overview]
Message-ID: <rmk74v72kn.fsf@mlinux.pd.infn.it> (raw)
In-Reply-To: mailman.195.1071679031.868.help-gnu-emacs@gnu.org

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

  parent reply	other threads:[~2003-12-17 17:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.195.1071679031.868.help-gnu-emacs@gnu.org>
2003-12-17 16:26 ` GNU emacs locks files modified with CVS Kevin Rodgers
2003-12-17 19:03   ` gebser
2003-12-17 16:41 ` Pepijn Kenter
2003-12-17 17:54 ` Maurizio Loreti [this message]
2003-12-18 17:19   ` Kevin Rodgers
     [not found] <mailman.138.1071587578.868.help-gnu-emacs@gnu.org>
2003-12-16 14:51 ` Pepijn Kenter
2003-12-16 16:26   ` gebser
2003-12-17  6:42   ` Maurizio Loreti
2003-12-17 15:34     ` gebser
2003-12-15 12:25 Pepijn Kenter
2003-12-15 18:04 ` Kevin Rodgers
2003-12-16  9:44   ` Pepijn Kenter
2003-12-16 14:10     ` gebser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=rmk74v72kn.fsf@mlinux.pd.infn.it \
    --to=mlo@foobar.it \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).