zsh-workers
 help / color / mirror / code / Atom feed
From: Itai Seggev <is@cs.hmc.edu>
To: zsh-workers@sunsite.dk
Subject: get _files to work/bug in subversion in completion
Date: Fri, 8 Jul 2005 23:07:26 -0700 (PDT)	[thread overview]
Message-ID: <Pine.GSO.4.58.0507082254030.13687@turing> (raw)


I would like to get zsh to provide me with file completion if the
_complete fails to find anything. According to

http://zsh.sourceforge.net/FAQ/zshfaq04.html#l50

all I need to do is add _files to the end of my completion list.
Thus, I use

zstyle ':completion:*::::' completer _complete _ignored _files

but this doesn't seem to change anything. By analogy with the suggestion in

http://www.zsh.org/mla/users//2004/msg01039.html

I try to define a _complete_first command

_complete_first() {
  _complete "$@"
  return 1
}
zstyle ':completion:*::::' completer _complete_first _files _ignored

to force _files to always run. This makes files appear alongside
arguments, but there no files appear in the situations where
completion fails.

In particular, if I do a

svn ci -F [tab]

to try to get a list of of possible files to use as my changelog, zsh
never completes anything. I think this is a bug...
--
Itai

Itai Seggev, University of Chicago, Department of Physics

In 1997 a group of programmers started writing a desktop environment
to fix a travesty they didn't create.  Their program promptly found
its way onto un*x systems everywhere. Today, still opposed by a
software monopolist, they survive as soldiers of fortune.  If you share
their vision, if you know you can help, and if you can connect to
internet, maybe you can join... the K-Team.


             reply	other threads:[~2005-07-09 16:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-09  6:07 Itai Seggev [this message]
2005-07-09 17:49 ` Bart Schaefer
2005-07-09 21:27   ` Itai Seggev

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=Pine.GSO.4.58.0507082254030.13687@turing \
    --to=is@cs.hmc.edu \
    --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).