Date: Tue, 11 Jul 2006 17:02:49 +0100 From: Alex Zbyslaw <xfb52@dial.pipex.com> To: Giorgos Keramidas <keramida@ceid.upatras.gr> Cc: Peter <petermatulis@yahoo.ca>, freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: aterm -e screen does not source .bashrc Message-ID: <44B3CBA9.2050709@dial.pipex.com> In-Reply-To: <20060711144739.GA79957@gothmog.pc> References: <20060711125448.GA77175@gothmog.pc> <20060711130938.72503.qmail@web60014.mail.yahoo.com> <20060711132336.GB77495@gothmog.pc> <44B3B6B1.2050801@dial.pipex.com> <20060711144739.GA79957@gothmog.pc>
next in thread | previous in thread | raw e-mail | index | archive | help
Giorgos Keramidas wrote: >Agreed. My current .bash_profile is basically a minimal wrapper around >.bashrc these days: > >% gothmog % cat -n .bash_profile >% 1 # Startup file for login instances of the bash(1) shell. >% 2 # $RCS: giorgos/.bash_profile,v 1.10 2005/07/10 21:10:39 giorgos Exp $ >% 3 >% 4 # First of all, run a .bashrc file if it exists. >% 5 test -f ~/.bashrc && . ~/.bashrc >% 6 >% 7 # The following section should be pretty minimal, if present at all. >% 8 mesg y >/dev/null 2>&1 >% 9 /usr/bin/true >% gothmog % > > > I've found the distinction quite useful since, for example, I only want to run ssh-agent when logging in on the console, but not if I su, say. (I also share all my shell configuration files with my root identity, so I would expect to su on the console). Also, stuff like limits and exported environment variables only need to get set in the shell that owns all the others. And if you have things like mail notifications, or fortune, they just become irritating if you get them in every single xterm. --Alex
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44B3CBA9.2050709>