home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: gnu.bash.bug
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!spserv.bbn.com!jjd
- From: jjd@spserv.bbn.com (James J Dempsey)
- Subject: Re: rsh, rcp with bash
- Message-ID: <9207301331.AA02814@life.ai.mit.edu>
- Sender: gnulists@ai.mit.edu
- Organization: GNUs Not Usenet
- References: <2A7691FE.7354@tct.com>
- Distribution: gnu
- Date: Thu, 30 Jul 1992 13:31:35 GMT
- Approved: bug-bash@prep.ai.mit.edu
- Lines: 39
-
- > According to chet@po.cwru.edu:
- > >Bash attempts to source the .bashrc for non-interactive shells running
- > >rsh and rcp so things like $PATH get set.
- >
- > ... which is, in my opinion, a BIG mistake.
- >
- > Thus the following patch to Bash 1.12 to eliminate that behavior:
-
- I strongly disagree with you.
-
- Rsh is almost useless to me if I can't get my shell to run some init
- file to set PATH and other environment variables.
-
- If you disable bash from running an init file, there is no way to get
- the behaviour I want.
-
- If you leave it the way it is, you can get the behaviour you want
- in non-interactive mode by wrapping
-
- if [ "$PS1" ]; then
-
- < your entire .bashrc >
-
- fi
-
- around your entire init file.
-
-
- Shells like sh and ksh that don't run any init file are really useless
- to me. Shells like tcsh, bash and csh do the right thing, IMHO.
-
- Given that this is such a religious issue, it seems best to leave it
- the way it is. This way either methodology can be implemented in the
- .bashrc file. Changing it to not source .bashrc leaves many of us out
- in the cold.
-
- --Jim Dempsey--
- jjd@bbn.com
-
-