zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: _pon, poff
Date: Fri, 27 Oct 2006 15:46:56 +0100	[thread overview]
Message-ID: <200610271446.k9REkv05013058@news01.csr.com> (raw)
In-Reply-To: <slrnek98km.ffd.joerg@alea.gnuu.de>

=?UTF-8?Q?J=C3=B6rg?= Sommer wrote:
> Hello Clint,
> 
> Clint Adams <clint@zsh.org> wrote:
> >    '(-q --quick)'{-q,--quick}'[hangs up after all ip-up scripts are run]' \
> > -  '1:provider to call:(${provider[@]})'
> > +  '1:provider to call:_files -W /etc/ppp/peers'
> 
> Only for my understanding: Why you can use _files here? Doesn't this tag
> the completions as files even though they are hosts? Does this cause any
> problems?

The basic behaviour of _files is just to add the filenames as strings.
There is additional behaviour (showing types, etc.), but it relies on
being able to find the file added.  If the completion system doesn't
find the file it will just fall back to treating it like an ordinary
string.  In this case, it actually will find the file; but all that's
likely to happen is a few extra things show up.  The most distracting
possibility is if you're using the file-list style I added.  Then you
might see long listings of the file in that directory.  Outside listings,
however, you shouldn't see any problems.

-- 
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-10-30 15:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-07  8:50 Clint Adams
2006-10-29 12:46 ` Jörg Sommer
2006-10-27 14:46   ` 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=200610271446.k9REkv05013058@news01.csr.com \
    --to=pws@csr.com \
    --cc=zsh-workers@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).