zsh-workers
 help / color / mirror / code / Atom feed
From: Andrej Borsenkow <borsenkow.msk@sni.de>
To: schaefer@nbn.com
Cc: Zoltan Hidvegi <hzoli@cs.elte.hu>, zsh-workers@math.gatech.edu
Subject: Re: sh compatibility again :->
Date: Mon, 12 Aug 1996 10:20:09 +0400 (MOW)	[thread overview]
Message-ID: <Pine.SV4.3.95.960812101243.20050A-100000@itsrm1> (raw)
In-Reply-To: <960811213634.ZM4881@candle.brasslantern.com>

On Sun, 11 Aug 1996, Bart Schaefer wrote:

> 
> } > But the following things could probably be fixed 
> } > 
> } > 4. Traditional /bin/sh interprets `set -' as set +xv.
> } 
> } OK.  I've changed that.  set - will be the same as set +xv and
> } set - args will be the same as set +xv -- args.
> 
> Hmm.  So what's the approved way of setting $1 to "-x"?  `set -- -x`?
> And is `set --` equivalent to `shift $#`, since `set -` is not?
> 
> Are you sure `set - args` should act like `set +xv -- args`?
> 

Well, /bin/sh behaves execatly this way.

> I can't say I'm entirely excited about this change.
> 

It is lonely `set -' which have this effect. Just the same, as lonely `set
+' does *not* sets $1 to + but rather outputs all parameter names. If I
try `set + foo', it sets $1 to `foo'. So `set -' could just follow the
suit.

Greetings

-------------------------------------------------------------------------
Andrej Borsenkow 		Fax:   +7 (095) 252 01 05
SNI ITS Moscow			Tel:   +7 (095) 252 13 88

NERV:  borsenkow.msk		E-Mail: borsenkow.msk@sni.de
-------------------------------------------------------------------------



  parent reply	other threads:[~1996-08-12  6:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-07-31 21:11 Announcement draft Zoltan Hidvegi
1996-07-31 22:15 ` Zefram
1996-08-01  6:36 ` Bas V. de Bakker
1996-08-01  8:31   ` Peter Stephenson
1996-08-01  9:04     ` Running zsh as sh (Was: Announcement draft) Bas V. de Bakker
1996-08-01  9:10     ` Announcement draft Andrej Borsenkow
1996-08-01 13:49       ` Here docs Peter Stephenson
1996-08-01 14:07         ` Zoltan Hidvegi
1996-08-01 16:27           ` More Configure problems Peter Stephenson
1996-08-01 17:40             ` Peter Stephenson
1996-08-01 17:55               ` Zoltan Hidvegi
1996-08-01 21:03                 ` Zoltan Hidvegi
1996-08-01 23:30                   ` Zoltan Hidvegi
1996-08-02  8:32                   ` Peter Stephenson
1996-08-02 10:03                     ` Andrej Borsenkow
1996-08-02 13:29                       ` Zoltan Hidvegi
1996-08-02  1:03             ` Zefram
1996-08-01 14:42   ` Announcement draft Zoltan Hidvegi
1996-08-08 15:13 ` sh compatibility again :-> Andrej Borsenkow
1996-08-12  2:18   ` Zoltan Hidvegi
1996-08-12  4:36     ` Bart Schaefer
1996-08-12  5:00       ` Zefram
1996-08-12  6:01         ` Bart Schaefer
1996-08-12  6:34           ` Bart Schaefer
1996-08-12  6:20       ` Andrej Borsenkow [this message]
1996-08-12 15:29 whukriede

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=Pine.SV4.3.95.960812101243.20050A-100000@itsrm1 \
    --to=borsenkow.msk@sni.de \
    --cc=hzoli@cs.elte.hu \
    --cc=schaefer@nbn.com \
    --cc=zsh-workers@math.gatech.edu \
    /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).