zsh-workers
 help / color / mirror / code / Atom feed
From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: pws@ifh.de (Peter Stephenson)
Cc: zsh-workers@math.gatech.edu
Subject: Re: bug, limitation, ...?
Date: Fri, 26 Jul 1996 14:00:50 +0200 (MET DST)	[thread overview]
Message-ID: <199607261200.OAA04221@bolyai.cs.elte.hu> (raw)
In-Reply-To: <199607260844.KAA19446@hydra.ifh.de> from Peter Stephenson at "Jul 26, 96 10:44:05 am"

> Somebody was complaining to me on the S-Bahn yesterday evening that he
> couldn't do:
> 
> % set foo
> % print ${1[0]}
> zsh: closing brace expected
> 
> (I think this question has cropped up before, in fact, but that was
> long before Zoltan's parameter substitution improvements.)  It would
> be nice if numerical parameters were as much like `other' scalar
> parameters as possible.  (OK, they're really array elements, but the
> mode of addressing suggests that should be hidden from the user; after
> all, direct assignment works.)  Still, the world is not a nice place.
> If it turns out a change would be tantamount to allowing ${argv[0][0]}
> it's probably too much, at least for now.

Well, I have already fixed this, and in fact ${argv[0][0]} will work in pre4,
and more:

"${${(M)${(f@)$(<builtin.pro)}:%char*}[2][(w)3]}"

expands to the third word of the second line of builtin.pro which begins
with char.

This is really a side effect of a fix to the ${foo[1]} bug when foo is
unset.  Peter had a fix for that as well but I did not like that much.  It
was quite easy to do that, but big chunks of the code had to be reindented
so the diff's may look big.

Zoltan



      reply	other threads:[~1996-07-26 12:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-07-26  8:44 Peter Stephenson
1996-07-26 12:00 ` Zoltan Hidvegi [this message]

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=199607261200.OAA04221@bolyai.cs.elte.hu \
    --to=hzoli@cs.elte.hu \
    --cc=pws@ifh.de \
    --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).