zsh-users
 help / color / mirror / code / Atom feed
From: Adam Spiers <adam@thelonious.new.ox.ac.uk>
To: zsh-users@sunsite.auc.dk
Subject: Re: strange glob expansion
Date: Fri, 3 Sep 1999 02:40:39 +0100	[thread overview]
Message-ID: <19990903024039.A23433@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <990901174608.ZM19896@candle.brasslantern.com>; from Bart Schaefer on Wed, Sep 01, 1999 at 05:46:08PM +0000

Bart Schaefer (schaefer@candle.brasslantern.com) wrote:
> On Sep 1, 10:11am, Hubert Canon wrote:
> } Subject: strange glob expansion
> }
> } I tried something like this :
> } 
> } % echo .scwm/(chan*|**/scwmrc*)
> 
> Directory separators can't be used inside parentheses.  Parenthesized
> patterns match within one level of file hierarchy only.  (The '/' may
> still be useful when matching against strings, as in a `case' label, but
> doesn't work when globbing.)

On a related topic, the following puzzles me:

% cd /usr/lib/perl5/site_perl/5.005
% echo L*
LWP LWP.pm Lingua                 (letting you know what's there)
% echo L(*/)
zsh: no matches found: L(*/)      (why doesn't this match the 2 dirs?)
% echo L(*/)#
LWP LWP.pm Lingua                 (why does this match a file?)
% echo L(*/)z
LWP LWP.pm Lingua                 (HUH?)

The upshot of this is that to match all Perl modules starting with `L'
below the cwd, I have to use L{*/**/*,}.pm instead of L**/*.pm.

This is with zsh 3.1.6, no patches.

% uname -a
Linux pulse.localdomain 2.2.10-ac2 #1 Tue Jun 22 10:36:51 BST 1999 i686 unknown

P.S. Is there any movement on making an anonymous CVS tree available?
I'll have a few bug-fixing patchlets ready to submit to zsh-workers
soon, but the rate of development on the list is so ferociously high
that I can't keep up with all the patches.  There have probably been
20 or so already since pws-2!

P.P.S. What version would you rather have patches against?  3.1.6
clean?  The latest pws?

-- 
--- adam@spiers.net --- musician and hacker --- http://www.new.ox.ac.uk/~adam/
echo '$_=bless[q]]],q;_;;sub s;{local$_=shift;push@$_,++$0,pop(@$_).$s;;$_}($,
=eval((join"\$_->[",qw)Just Another Perl Hacker)).q)$_->[1]]]])))=~s~((?<=.(?{
++$*})))?_::~$*&&$"~egx,print""=>""=>'|perl -ln0e';s;s\;;_::AUTOLOAD$1;g;eval'


  parent reply	other threads:[~1999-09-03  1:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-01  8:11 Hubert Canon
1999-09-01 17:46 ` Bart Schaefer
1999-09-02 10:15   ` Hubert Canon
1999-09-02 15:01     ` Bart Schaefer
1999-09-03  2:48       ` dado
1999-09-03  4:54         ` Bart Schaefer
1999-09-03 12:11       ` Hubert Canon
1999-09-03 14:15         ` Bart Schaefer
1999-09-03 14:34           ` Hubert Canon
1999-09-03  1:40   ` Adam Spiers [this message]
1999-09-03  4:34     ` Bart Schaefer
1999-09-03  8:55       ` Peter Stephenson
1999-09-05 21:07         ` Adam Spiers

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=19990903024039.A23433@thelonious.new.ox.ac.uk \
    --to=adam@thelonious.new.ox.ac.uk \
    --cc=adam@spiers.net \
    --cc=zsh-users@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).