zsh-workers
 help / color / mirror / code / Atom feed
From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: schaefer@brasslantern.com (Bart Schaefer)
Cc: zsh-workers@math.gatech.edu
Subject: Re: foo(:...) and foo~ glob
Date: Sat, 2 May 1998 22:22:31 -0500 (CDT)	[thread overview]
Message-ID: <199805030322.WAA11570@hzoli.home> (raw)
In-Reply-To: <980502152731.ZM28509@candle.brasslantern.com> from Bart Schaefer at "May 2, 98 03:27:31 pm"

> On May 2,  3:27pm, Zoltan Hidvegi wrote:
> } Subject: foo(:...) and foo~ glob
> }
> } After this change:
> } 
> } Sun Apr  5 20:00:40 1998  Andrew Main  <zefram@fysh.org>
> } 
> } the (:quals) syntax no longer works.
> 
> Does this also mean that either/both of the following are broken?
> 
> 	echo ${pref}**/CVS(:h) | sed 's/CVS//'
> 
> 	case $(tty)(:t) in

Perhaps I was not very clear.  Both of these works.  The (:...) syntax
triggers globbing, which means it does not work on words which are not
existing filenames.  The later $(tty)(:t) example works differently than
before, although you'll not notice it: zsh now looks at the disk if the
result of tty exists before applying the qualifier, while before the
qualifier was applied unconditionally.  Since ttyp gives you an existing
device, this does not make any difference here.  The difference is in
things like

echo asdfg(:s/g/h/)

gives you

zsh: no matches found: asdfg(:s/g/h/)

instead of asdfh if you do not have a file called asdfg in your current
directory.  Zefram is right in that the old behaviour was not very well
documented, which is really my fault, since I added this in 2.6-beta20.

Zoli


  reply	other threads:[~1998-05-03  3:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-05-02 20:27 Zoltan Hidvegi
1998-05-02 22:27 ` Bart Schaefer
1998-05-03  3:22   ` Zoltan Hidvegi [this message]
1998-05-05  8:53   ` Andrew Main
1998-05-05  8:48 ` Andrew Main

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=199805030322.WAA11570@hzoli.home \
    --to=hzoli@cs.elte.hu \
    --cc=schaefer@brasslantern.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).