On Saturday, September 13, 2003, at 03:21 AM, der.hans wrote:
> Am 12. Sep, 2003 schw=E4tzte Kurt Granroth so:
>
>> <wild supposition>maybe sh uses the selective expand policy while csh=20=

>> always
>> expands.  bash and ksh use sh behavior and zsh uses csh.</wild=20
>> supposition>
>
> Ah, didn't relize that zsh is based on csh ( or some csh derivative ).
>
> I thought zsh is sh compatible and derived.

zsh is actually created from scratch with the goal to have the best=20
parts of all
the other shells.  For the most part, it comes across as being an sh=20
derivative
since (also for the most part) csh sucks.  But tcsh does have very nice=20=

completion
and a more consistent globbing than, say, bash, so zsh co-opted that.

> I know it's not due to programmable completion as I don't use that (=20=

> foolish
> of me because it rocks and it's the reason I kept thinking about=20
> moving to
> zsh ), but bash might still know several networked commands such as=20
> ssh and
> rsh. Maybe they eat the error and somehow do the right thing...

The programmable completion is actually why I switched to zsh in the=20
first place.
I always liked how tcsh did that but liked the sh-style of everything=20
else.  For me,
zsh was the perfect compromise.

I get around the globbing issue by aliasing certain commands (like scp)=20=

to 'noglob scp'
since I *know* that I'm going to be using "remote" wildcards on them=20
quite a bit.=