🚀 go-pugleaf

In  <7238@sugar.hackercorp.com> (9 Dec),
Peter da Silva (peter@sugar.hackercorp.com) writes:
> In article <1990Dec9.090708.20063@agate.berkeley.edu> pete@violet.berkeley.edu (Pete Goodeve) writes:
|>
|> discussing pipe metacharacter selection]
>
> Put it in his shell RC file, and then all his interactive shells will have
> it. That's effectively "global", without breaking scripts:
>
|> [....]
> [No,] batch scripts need to have a standard environment, particularly for things
> like metacharacters.
>
> If you have a global PIPECHAR variable, it needs to be ignored when not in
> interactive mode. (This is the MOST hosed feature of the C shell on UNIX, that
> scripts have to deal with whatever wacko stuff a user puts in their .cshrc)
> --
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?

The problem is you have to deal with scripts created by the user for his
own convenience, as well as scripts imported from elsewhere.  The latter
will expect some kind of standard, but I do NOT want to have to remember
two conventions -- my own favourite and the "standard" -- one for
interaction, and the other for hacking out quick scripts, thank you.

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".
                                            -- Pete --