zsh-users
 help / color / mirror / code / Atom feed
From: "Andrei A. Voropaev" <av@simcon-mt.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: frederik@ofb.net, zsh-users@sunsite.dk
Subject: Re: completion for darcs
Date: Tue, 5 Apr 2005 16:58:58 +0200	[thread overview]
Message-ID: <20050405145858.GA23124@vandal.simcon-mt.de> (raw)
In-Reply-To: <1050405144010.ZM15148@candle.brasslantern.com>

On Tue, Apr 05, 2005 at 02:40:10PM +0000, Bart Schaefer wrote:
> On Apr 5, 12:29am, Frederik Eaton wrote:
> }
> } Shouldn't it be possible to just tell zsh that when there are no
> } completions for an argument, it should fall back to completing files?
> 
> Sure.  And it is.  I'm surprised no one has mentioned this yet.  Just
> put "_files" directly into your "completer" zstyle somewhere.  E.g.:
> 
> zstyle ':completion:*' completer \
>     _oldlist _expand _complete _match _ignored _files _approximate _prefix
> 
> Where you place it will determine the precedence taken by file completion
> with respect to "repairs" (like partial and approximate matching) done on
> the completions suggested by the more context-specific completer selected
> by _complete.

Yahoo! :) Works perfectly :)

-- 
Minds, like parachutes, function best when open


  reply	other threads:[~2005-04-05 15:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-01  8:06 Andrei A. Voropaev
2005-04-01  8:09 ` Andrei A. Voropaev
2005-04-01  9:32   ` Antoine Calando
2005-04-01 12:36     ` Dominic Mitchell
2005-04-01 13:18       ` Antoine Calando
2005-04-01 21:37         ` Sami Samhuri
2005-04-05  7:29         ` Frederik Eaton
2005-04-05 14:40           ` Bart Schaefer
2005-04-05 14:58             ` Andrei A. Voropaev [this message]
2005-04-01 12:56     ` J
2005-04-01 13:32     ` Peter Stephenson
2005-04-01 13:51       ` Peter Stephenson

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=20050405145858.GA23124@vandal.simcon-mt.de \
    --to=av@simcon-mt.com \
    --cc=frederik@ofb.net \
    --cc=schaefer@brasslantern.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).