RE: PATCH: (was Re: _configure does not work)

[Sven Wischnowsky <wischnow@xxxxxxxxxxxxxxxxxxxxxxx>]

Andrej Borsenkow wrote:

> > This is slightly modeled after globbing behavior: anchors of `*'
> > patterns separate parts like slashes separate pathname components.
> > Inside the word they all have to be typed explicitly.
> >
> > Personally, I like this behavior much better than the `* matches even
> > it's anchors' (I wanted this behavior from the beginning, so I
> > consider the patch to be a bug fix), because an important goal of
> > completion is to produce as few matches as possible -- even if this
> > may sound strange.
> >
> 
> Agreed. If only the manuals mentioned this as well ...

Yep, maybe...

Bye
 Sven

diff -u od/Zsh/compctl.yo Doc/Zsh/compctl.yo
--- od/Zsh/compctl.yo	Mon Mar  8 09:04:45 1999
+++ Doc/Zsh/compctl.yo	Tue Mar  9 14:57:08 1999
@@ -703,7 +703,8 @@
 that the pattern on the command line can match any number of characters
 in the trial completion. In this case the pattern must be anchored (on
 either side); the var(anchor) then determines how much of the trial
-completion is to be included.
+completion is to be included --- only the characters up to the next
+appearance of the anchor will be matched.
 
 Examples:
 
@@ -758,7 +759,8 @@
   -k '(comp.sources.unix comp.sources.misc ...)' ngroups))
 )
 The first specification says that tt(lpat) is the empty string, while
-tt(anchor) is a dot; tt(tpat) is tt(*), so this can match anything in
+tt(anchor) is a dot; tt(tpat) is tt(*), so this can match anything
+except for the `tt(.)' from the anchor in
 the trial completion word.  So in tt(c.s.u), the matcher sees tt(c),
 followed by the empty string, followed by the anchor `tt(.)', and
 likewise for the second dot, and replaces the empty strings before the

--
Sven Wischnowsky                         wischnow@xxxxxxxxxxxxxxxxxxxxxxx