zsh-users
 help / color / mirror / code / Atom feed
From: Jesper Holmberg <jeho5791@student.uu.se>
To: Zsh-users List <zsh-users@sunsite.dk>
Subject: Problem with complete-all
Date: Fri, 13 Aug 2004 09:45:26 +0200	[thread overview]
Message-ID: <20040813074526.GM1191@localhost> (raw)

I can't get complete-all to work as I would like it to. Perhaps I have
misunderstood what it's supposed to be doing, so I'll try to describe what
I want to accomplish.

I use the new completion system with menu-complete bound to <TAB>.
Suppose that I have a directory which is under CVS version control, and
that I have added a couple of files to this directory. If I now go: 

cvs add <TAB>

the completion system supplies one of the added files, which is very nice.
Pressing <TAB> again switches to the next added file, until I have cycled
through them all.

Now, what I thought would be possible to accomplish with complete-all
(bound to, say, '^Xx') would be that when I go:

cvs add ^Xx

all the files which have been added would be put on the command line at
the same time. However, what happens is that zsh beeps and nothing else,
not even an error message. Doing a 'describe-key-briefly' on '^Xx' shows
'all-matches'.

This is what I have in my .zshrc, taken from the manual:

zle -C all-matches complete-word _generic
bindkey '^Xx' all-matches
zstyle ':completion:all-matches:*' old-matches only
zstyle ':completion:all-matches::::' completer _all_matches

What am I doing wrong?

TIA,

Jesper


             reply	other threads:[~2004-08-13  7:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-13  7:45 Jesper Holmberg [this message]
2004-08-13  9:33 ` Oliver Kiddle
2004-08-13  9:58   ` Oliver Kiddle
2004-08-16  6:46   ` Jesper Holmberg
2004-08-17 10:28     ` Jesper Holmberg

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=20040813074526.GM1191@localhost \
    --to=jeho5791@student.uu.se \
    --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).