zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh users <zsh-users@sunsite.dk>
Subject: Re: error in 19.3.1
Date: Wed, 20 Sep 2006 12:02:58 +0100	[thread overview]
Message-ID: <200609201102.k8KB2w3m011521@news01.csr.com> (raw)
In-Reply-To: <20060920124814.GA56989@dagan.sigpipe.cz>

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


      reply	other threads:[~2006-09-20 11:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-19 22:28 Roman Neuhauser
2006-09-20  9:26 ` Peter Stephenson
2006-09-20 12:48   ` Roman Neuhauser
2006-09-20 11:02     ` Peter Stephenson [this message]

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=200609201102.k8KB2w3m011521@news01.csr.com \
    --to=pws@csr.com \
    --cc=zsh-users@sunsite.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).