error in 19.3.1

error in 19.3.1

[Roman Neuhauser]

This is near the end of 19.3.1:

For example:

zstyle -e ':completion:*' completer '
    if [[ $words[1] = cvs ]]; then
      reply=(_complete)
    else
      reply=(_complete _approximate)
    fi'

uses the value `_complete' for the completer style in most contexts, but
the value `_complete _approximate' when the first word on the command
line is `cvs'.

-- 
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man.  You don't KNOW.
Cause you weren't THERE.             http://bash.org/?255991

Re: error in 19.3.1

[Peter Stephenson]

Roman Neuhauser wrote:
> This is near the end of 19.3.1:

(The section numbers aren't particularly easy to trace back to the
documentation source, so names are probably more convenient.)

> For example:
> 
> zstyle -e ':completion:*' completer '
>     if [[ $words[1] = cvs ]]; then
>       reply=(_complete)
>     else
>       reply=(_complete _approximate)
>     fi'
> 
> uses the value `_complete' for the completer style in most contexts, but
> the value `_complete _approximate' when the first word on the command
> line is `cvs'.

You mean the code should be the other way round?

Index: Doc/Zsh/compsys.yo
===================================================================
RCS file: /cvsroot/zsh/zsh/Doc/Zsh/compsys.yo,v
retrieving revision 1.190
diff -u -r1.190 compsys.yo
--- Doc/Zsh/compsys.yo	21 Aug 2006 14:24:49 -0000	1.190
+++ Doc/Zsh/compsys.yo	20 Sep 2006 09:24:53 -0000
@@ -593,9 +593,9 @@
 
 example(zstyle -e ':completion:*' completer '
     if [[ $words[1] = cvs ]]; then
-      reply=(_complete)
-    else
       reply=(_complete _approximate)
+    else
+      reply=(_complete)
     fi')
 
 uses the value `tt(_complete)' for the tt(completer) style in most

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


To access the latest news from CSR copy this link into a web browser:  http://www.csr.com/email_sig.php

Re: error in 19.3.1

[Peter Stephenson]

Roman Neuhauser wrote:
> > You mean the code should be the other way round?
>  
>     Only if the behavior described in the text actually makes sense,
>     that is, is this setting useful?

Here's an example I actually use, plus another comment.

Index: Doc/Zsh/compsys.yo
===================================================================
RCS file: /cvsroot/zsh/zsh/Doc/Zsh/compsys.yo,v
retrieving revision 1.190
diff -u -r1.190 compsys.yo
--- Doc/Zsh/compsys.yo	21 Aug 2006 14:24:49 -0000	1.190
+++ Doc/Zsh/compsys.yo	20 Sep 2006 11:02:09 -0000
@@ -589,19 +589,15 @@
 the internals of completion functions (see
 ifzman(see zmanref(zshcompwid))\
 ifnzman(noderef(Completion Widgets)))\
-).  For example:
+).  For example,
 
-example(zstyle -e ':completion:*' completer '
-    if [[ $words[1] = cvs ]]; then
-      reply=(_complete)
-    else
-      reply=(_complete _approximate)
-    fi')
+example(tt(ztyle -e ':completion:*' hosts 'reply=($myhosts)'))
 
-uses the value `tt(_complete)' for the tt(completer) style in most
-contexts, but the value `tt(_complete _approximate)' when the first word
-on the command line is `tt(cvs)'.  This is probably more conveniently done
-by specifying the style for two different contexts.  This form can be
+This forces the value of the tt(hosts) style to be read from the
+variable tt(myhosts) each time a host name is needed; this is useful
+if the value of tt(myhosts) can change dynamically.
+For another useful example, see the example in the description of the
+tt(file-list) style below.  This form can be
 slow and should be avoided for commonly examined styles such
 as tt(menu) and tt(list-rows-first).
 
@@ -3313,8 +3309,8 @@
 an option taking multiple arguments may be
 given in this form.  If the var(pattern) is empty (i.e., tt(:*:)), all
 the remaining words on the line are to be completed as described by the
-var(action); otherwise, all the words up to a word matching the
-var(pattern) are to be completed using the var(action).
+var(action); otherwise, all the words up to and including a word matching
+the var(pattern) are to be completed using the var(action).
 
 Multiple colons are treated as for the `tt(*:)var(...)' forms for
 ordinary arguments:  when the var(message) is preceded by two colons,

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


To access the latest news from CSR copy this link into a web browser:  http://www.csr.com/email_sig.php

Re: error in 19.3.1

[Roman Neuhauser]

# pws@csr.com / 2006-09-20 10:26:43 +0100:
> Roman Neuhauser wrote:
> > This is near the end of 19.3.1:
> 
> (The section numbers aren't particularly easy to trace back to the
> documentation source, so names are probably more convenient.)
 
    Aha, sorry.

> > zstyle -e ':completion:*' completer '
> >     if [[ $words[1] = cvs ]]; then
> >       reply=(_complete)
> >     else
> >       reply=(_complete _approximate)
> >     fi'
> > 
> > uses the value `_complete' for the completer style in most contexts, but
> > the value `_complete _approximate' when the first word on the command
> > line is `cvs'.
> 
> You mean the code should be the other way round?
 
    Only if the behavior described in the text actually makes sense,
    that is, is this setting useful? Not if the _approximate completer
    bypasses the smarts that make _cvs offer only unversioned files to
    cvs add, only versioned (or scheduled for addition) files to cvs ci,
    etc.
    
    I don't actually know what will _cvs do with this completer
    (svn everywhere I look), I'm just saying this should be considered.

-- 
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man.  You don't KNOW.
Cause you weren't THERE.             http://bash.org/?255991