From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Still problems with scriptname (presumably)
Date: Tue, 4 Apr 2000 14:16:11 +0200 (MET DST) [thread overview]
Message-ID: <200004041216.OAA13494@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Peter Stephenson's message of Mon, 03 Apr 2000 21:32:35 +0100
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.
Note: no `PATCH:' in the subject...
I was about to send/commit the patch below (which is kinda brute
force, setting scriptname to zsh when there is a -c option on the
command line).
But then I tried ksh and bash. ksh doesn't give me an error (?!?) and
bash does the same as zsh currently does.
I don't need to say that compatibility to bash doesn't interest me, do I?
So, should I commit the change?
Bye
Sven
Index: Src/init.c
===================================================================
RCS file: /cvsroot/zsh/zsh/Src/init.c,v
retrieving revision 1.1.1.51
diff -u -r1.1.1.51 init.c
--- Src/init.c 2000/03/23 04:22:57 1.1.1.51
+++ Src/init.c 2000/04/04 12:09:26
@@ -222,6 +222,7 @@
cmd = *argv;
opts[INTERACTIVE] &= 1;
opts[SHINSTDIN] = 0;
+ scriptname = ztrdup("zsh");
} else if (**argv == 'o') {
if (!*++*argv)
argv++;
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-04-04 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-04 12:16 Sven Wischnowsky [this message]
2000-04-04 19:31 ` Peter Stephenson
-- 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=200004041216.OAA13494@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--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).