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: Fri, 5 Feb 1999 08:45:57 +0100 (MET) [thread overview]
Message-ID: <199902050745.IAA10808@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Thu, 4 Feb 1999 08:11:07 -0800
Bart Schaefer wrote:
> The manual says of GLOB_COMPLETE, "If no matches are found, a `*' is added
> to the end of the word or inserted at the cursor if tt(COMPLETE_IN_WORD)
> is set, and expansion is attempted again." Now, (I*)* _IS_ a glob pattern,
> so this makes sense.
>
> That also means that with globcomplete,
>
> zsh% echo (I)<TAB>
> zsh% echo INSTALL
>
> which in fact is what happens. [[ INSTALL = (I) ]] is definitely false ...
> is globcomplete really using pattern matching the way you say?
Yes, but [[ INSTALL = (I)* ]] is true. I think we should just make
this clearer in the docs.
Bye
Sven
--- od/Zsh/options.yo Wed Feb 3 12:07:31 1999
+++ Doc/Zsh/options.yo Fri Feb 5 08:44:22 1999
@@ -331,11 +340,12 @@
pindex(GLOB_COMPLETE)
item(tt(GLOB_COMPLETE))(
When the current word has a glob pattern, do not insert all the words
-resulting from the expansion but cycle through them like
-tt(MENU_COMPLETE). If no matches are found, a `tt(*)' is added to the end of the
-word or inserted at the cursor if tt(COMPLETE_IN_WORD) is set, and expansion
-is attempted again. Using patterns works not only for files but for all
-completions, such as options, user names, etc.
+resulting from the expansion but collect matches as for completion and
+cycle through them like tt(MENU_COMPLETE). If no matches are found, a
+`tt(*)' is added to the end of the word or inserted at the cursor if
+tt(COMPLETE_IN_WORD) is set, and completion is attempted again using
+pattern matching. Since this doesn't use globbing, it not only for
+files but for all completions, such as options, user names, etc.
)
pindex(GLOB_DOTS)
cindex(globbing, of . files)
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-02-05 7:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-05 7:45 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-02-05 8:58 Sven Wischnowsky
1999-02-04 8:06 Sven Wischnowsky
1999-02-04 16:11 ` Bart Schaefer
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=199902050745.IAA10808@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).