🚀 go-pugleaf

In article <1990Dec10.084228.25707@agate.berkeley.edu> pete@violet.berkeley.edu (Pete Goodeve) writes:
> Mmm, but wait a minute... .rc files SHOULD apply to ALL shells in an
> environment (and in this case I think unix has it right...(:-)), so
> scripts would be affected too.  If they don't, how do you let scripts use
> things like aliases?

You don't. If you want your script to use your aliases then you should
explicitly load in the .rc file. Normally scripts shouldn't see aliases.

The way you fix this in UNIX is make your .cshrc look like:


	if ($?prompt) then
		source ~/.prompt
		source ~/.aliases
		set ignoreeof
		set noclobber
		set history=21
	endif

That way all the convenience stuff only gets set for interactive shells. I
do system and software support for about 400 people, and a lot of the problems
I get are caused by people putting weird shit in their .cshrc.

If you MUST have your aliases, load them explicitly. The standard AmigaShell
gets this right, as does the UNIX ksh.

> I was assuming that a script that needed a particular PIPECHAR would have
> a line enforcing that, so there would be no confusion.  That's what I
> meant by "BOTH".

No, the default PIPECHAR for non-interactive shells should be fixed. Because
most people don't change it and they'll forget to put the "default" in.
-- 
Peter da Silva.   `-_-'
<peter@sugar.hackercorp.com>.