zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Fun with zsh (Re: Associative array ordering (Re: Example function))
Date: Thu, 4 Feb 1999 09:06:09 +0100 (MET)	[thread overview]
Message-ID: <199902040806.JAA14145@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Wed, 3 Feb 1999 09:38:06 -0800


Bart Schaefer wrote:

> On Feb 3,  4:00pm, Sven Wischnowsky wrote:
> } Subject: Re: Fun with zsh (Re: Associative array ordering (Re: Example fun
> } 
> } Bart Schaefer wrote:
> } 
> } > Following application of your patch, using 3.1.5-pws-6 zsh -f,
> } > 
> } >     zsh% foo=('(I*)<TAB>
> } > 
> } > only feeps
> } 
> } Whew. The first behavior is the correct one, since the completion code 
> } should take the `(I*)' as the prefix of the string to complete and as
> } long as you don't have a file with a name starting with this, nothing
> } should be matched.
> 
> But I *DO* have a file beginning with "I" -- $PWD is the zsh source root,
> so the INSTALL file is there.  (I*) apparently isn't a glob pattern:
> 
> zagzig% echo (I*)    
> zsh: no matches found: (I*)
> zagzig% echo (I*|)
> INSTALL
> 
> So if your patch somehow makes (I*) complete, something weird is going on.

Something weird indeed: me again, forgetting to mention the option
globcomplete. *Only* if that option is set, (I*) will complete to
INSTALL.
Now one may argue that (I*) isn't a glob pattern so an option named
*glob*complete shouldn't make this happen. But the name of the option
has historical reasons, the option uses pattern matching (not
globbing) to match possible completions, and indeed:

  [[ INSTALL = (I*) ]] && echo yep, indeed

Ok?

Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~1999-02-04  8:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-04  8:06 Sven Wischnowsky [this message]
1999-02-04 16:11 ` Bart Schaefer
  -- strict thread matches above, loose matches on Subject: below --
1999-02-05  8:58 Sven Wischnowsky
1999-02-05  7:45 Sven Wischnowsky
1999-02-03 15:00 Sven Wischnowsky
1999-02-03 17:38 ` Bart Schaefer
1999-02-03 10:41 Sven Wischnowsky
1999-02-02 17:19 Sven Wischnowsky
1999-02-02 17:48 ` Bart Schaefer
1999-02-02 12:26 Sven Wischnowsky
1999-02-02 16:54 ` Bart Schaefer
     [not found] <jarausch-990202124256.A09694@numa1>
1999-02-02 11:59 ` Bart Schaefer
1999-02-02 12:10   ` Bart Schaefer
1999-02-02  8:01 Associative array ordering and selective unset (Re: Example function) Sven Wischnowsky
1999-02-02 11:31 ` Fun with zsh (Re: Associative array ordering (Re: Example function)) Bart Schaefer

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=199902040806.JAA14145@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).