Ray Lai [EMAIL PROTECTED] wrote:
No. Something is very wrong here. Why do your interactive shell
aliases propagate to random shells?
I export ENV=~/.profile
You need to wrap the contents into something like
case $- in *i*)
...
;;
esac
to keep them away from non-interactive shells.
On Mon, May 14, 2007 at 09:30:48PM +0200, Tobias Ulmer wrote:
I export ENV=~/.profile
That leads to 'funny' results. Do something like this in your
.profile:
if [ -o interactive ]; then
:
fi
$ cat /etc/profile
[ -o interactive ] [ $SHELL = /bin/ksh ] . /etc/ksh.kshrc
$
Ray Lai [EMAIL PROTECTED] wrote:
Allows me to alias rm='rm -i' and make update-patches. While I'm
here, add -f to other mv and rm commands.
Okay?
No. Something is very wrong here. Why do your interactive shell
aliases propagate to random shells?
I export ENV=~/.profile
On Mon, May 14, 2007 at 02:21:04PM -0400, Ray Lai wrote:
Ray Lai [EMAIL PROTECTED] wrote:
Allows me to alias rm='rm -i' and make update-patches. While I'm
here, add -f to other mv and rm commands.
Okay?
No. Something is very wrong here. Why do your interactive shell
Allows me to alias rm='rm -i' and make update-patches. While I'm
here, add -f to other mv and rm commands.
Okay?
-Ray-
Index: build/update-patches
===
RCS file: /cvs/ports/infrastructure/build/update-patches,v
retrieving revision
Ray Lai [EMAIL PROTECTED] wrote:
Allows me to alias rm='rm -i' and make update-patches. While I'm
here, add -f to other mv and rm commands.
Okay?
No. Something is very wrong here. Why do your interactive shell
aliases propagate to random shells?
--
Christian naddy Weisgerber
