Re: Bash .bashrc
On 07 Mar 2001, ktb wrote: On Wed, Mar 07, 2001 at 04:40:25PM -0500, Colin Cashman wrote: I have .bashrc set up to support color ls, but .bashrc isn't called when I log in. If I subsequently start a new shell, however, or 'source .bashrc' then the file is read and processed. What's the best way to handle this so it's done automagically upon logging in? Just throw source .bashrc onto the end of the .bash_profile file? I put the following in my .bash_profile if [ -f ~/.bashrc ]; then source ~/.bashrc fi hth, kent Is there any reason to use ~/.bash_profile, etc, rather than /etc/profile, if you are the only user on the system? Anthony -- Anthony Campbell - running Gnu/Debian Linux (Windows-free zone) For electronic books, skeptical essays, and over 120 book reviews, go to: http://www.cix.co.uk/~acampbell/ When I use a word ... it means just what I choose it to mean - neither more nor less. [Lewis Carroll]
RE: Bash .bashrc
On 07-Mar-2001 Colin Cashman wrote: I have .bashrc set up to support color ls, but .bashrc isn't called when I log in. If I subsequently start a new shell, however, or 'source .bashrc' then the file is read and processed. What's the best way to handle this so it's done automagically upon logging in? Just throw source .bashrc onto the end of the .bash_profile file? Why don't you just put it in your ~/.bash_profile? I have this alias in mine: ls='ls --color=auto -F -b -T 0 -N --show-control-chars' (note that some of the options in that ls are just there to make it handle accents more properly) -- Carlos Laviola - ICQ 55799523 pub 1024D/3516D372 2000-06-05 Carlos Laviola [EMAIL PROTECTED] Key fingerprint = 3BE1 6591 C78C 2AA4 31DD AEEF 6406 0227 3516 D372
Re: Bash .bashrc
On Wed, 07 Mar 2001 16:40:25 EST, Colin Cashman writes: What's the best way to handle this so it's done automagically upon logging in? Just throw source .bashrc onto the end of the .bash_profile file? IMHO: yes. cheers, rw -- / Ing. Robert Waldner | Network Engineer | T: +43 1 89933 F: x533 \ \ [EMAIL PROTECTED] |KPNQwest/AT | DSA key ID: C33A2BC0 /
RE: Bash .bashrc
I had this similar issue on my system. If you look at the bash_profile you will see some calls to the .bashrc...but they are commented out (why?) just uncomment them, and you are good to go -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 07, 2001 3:45 PM To: Colin Cashman Cc: debian-user@lists.debian.org Subject: Re: Bash .bashrc On Wed, 07 Mar 2001 16:40:25 EST, Colin Cashman writes: What's the best way to handle this so it's done automagically upon logging in? Just throw source .bashrc onto the end of the .bash_profile file? IMHO: yes. cheers, rw -- / Ing. Robert Waldner | Network Engineer | T: +43 1 89933 F: x533 \ \ [EMAIL PROTECTED] |KPNQwest/AT | DSA key ID: C33A2BC0 / -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bash .bashrc
Lo, on Wednesday, March 7, Colin Cashman did write: I have .bashrc set up to support color ls, but .bashrc isn't called when I log in. As expected. See bash's man page (specifically the `INVOCATION' section) for a discussion of the startup sequence. If I subsequently start a new shell, however, or 'source .bashrc' then the file is read and processed. What's the best way to handle this so it's done automagically upon logging in? Just throw source .bashrc onto the end of the .bash_profile file? Basically, yes. Richard
Re: Bash .bashrc
On Wed, Mar 07, 2001 at 04:40:25PM -0500, Colin Cashman wrote: I have .bashrc set up to support color ls, but .bashrc isn't called when I log in. If I subsequently start a new shell, however, or 'source .bashrc' then the file is read and processed. What's the best way to handle this so it's done automagically upon logging in? Just throw source .bashrc onto the end of the .bash_profile file? I put the following in my .bash_profile if [ -f ~/.bashrc ]; then source ~/.bashrc fi hth, kent -- From seeing and seeing the seeing has become so exhausted First line of The Panther - R. M. Rilke
