zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Still problems with scriptname (presumably)
Date: Tue, 04 Apr 2000 20:31:37 +0100	[thread overview]
Message-ID: <E12cZ32-0002qT-00.2000-04-04-20-31-36@mail3.svr.pol.co.uk> (raw)
In-Reply-To: "Sven Wischnowsky"'s message of "Tue, 04 Apr 2000 14:16:11 +0200." <200004041216.OAA13494@beta.informatik.hu-berlin.de>

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@pwstephenson.fsnet.co.uk>
Work: pws@CambridgeSiliconRadio.com
Web: http://www.pwstephenson.fsnet.co.uk


  reply	other threads:[~2000-04-04 19:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-04 12:16 Sven Wischnowsky
2000-04-04 19:31 ` Peter Stephenson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-04-06  8:26 Sven Wischnowsky
2000-04-05  8:15 Sven Wischnowsky
2000-04-05 19:21 ` Peter Stephenson
2000-04-03 20:32 Peter Stephenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E12cZ32-0002qT-00.2000-04-04-20-31-36@mail3.svr.pol.co.uk \
    --to=pws@pwstephenson.fsnet.co.uk \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).