Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Still problems with scriptname (presumably)
- X-seq: zsh-workers 10481
- From: Peter Stephenson <pws@xxxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: Still problems with scriptname (presumably)
- Date: Tue, 04 Apr 2000 20:31:37 +0100
- In-reply-to: "Sven Wischnowsky"'s message of "Tue, 04 Apr 2000 14:16:11 +0200." <200004041216.OAA13494@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
Sven Wischnowsky wrote:
> Peter Stephenson wrote:
> > % zsh -c 'echo '\' this_is_not_the_command_name
> > this_is_not_the_command_name:-1: unmatched '
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > this is the bit I object to, the error message is OK.
>
> But then I tried ksh and bash. ksh doesn't give me an error (?!?) and
> bash does the same as zsh currently does.
You're right, and in fact I've known about this for ages and mentioned it
before and was just thinking about it today and the penny still didn't
drop... Bourne shell derivatives when they use -c set $0 to the first
argument. That needs to be kept. There's no reason for an option which
will just add to the confusion.
I actually saw something like this somewhere else, where my $PS1 turned up
in an error message, and I can't remember where it was so I don't know if
that was a real bug.
--
Peter Stephenson <pws@xxxxxxxxxxxxxxxxxxxxxxxx>
Work: pws@xxxxxxxxxxxxxxxxxxxxxxxxx
Web: http://www.pwstephenson.fsnet.co.uk
Messages sorted by:
Reverse Date,
Date,
Thread,
Author