zsh-users
 help / color / mirror / code / Atom feed
From: "Jesper Nygårds" <jesper.nygards@gmail.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: Three questions about a completer
Date: Tue, 13 Sep 2016 21:18:06 +0200	[thread overview]
Message-ID: <CABZhJg_4b6GiCo1J3BHzL0ACwao5Q_-HQgnhuHjQowUF+FVemQ@mail.gmail.com> (raw)
In-Reply-To: <CABZhJg_kVjB4Wb1FH2xb7=dB8wU4pLLa8H7Jf4+p-Mahjv3wPA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 937 bytes --]

Sorry, this was an oversight on my part. When reducing the problem, I had
worked with a minimal .zshrc, and removed even the lines
autoload -U compinit
compinit

So now, at least, I get the completion to trigger. However, I still have
the same problem: hitting alt-e for menu-complete works, and hitting alt-E
for reverse-menu-complete works as well, but switching direction doesn't:
zsh puts a space after the alternative on the command line, indicating that
there is only one matching alternative. And I interpret that to mean that
it takes whatever happens to be on the command line after the initial
menu-complete, and tries to match that against the list it gets from the
invocation of reverse-menu-complete. Naturally, only the alternative
already on the command line matches.

So I suppose the problem is to make zsh realize it is calling "the same"
completer, only reversing the direction of the listing. Is this possible to
do?

  reply	other threads:[~2016-09-13 19:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-12 11:38 Jesper Nygårds
2016-09-12 20:53 ` Oliver Kiddle
2016-09-13 16:16   ` Jesper Nygårds
2016-09-13 19:18     ` Jesper Nygårds [this message]
2016-09-14  2:59       ` Bart Schaefer
2016-09-14  7:22         ` Jesper Nygårds
2016-09-14 16:39           ` Bart Schaefer
2016-09-14 20:32             ` Jesper Nygårds
2016-09-15  4:49               ` Bart Schaefer
2016-09-15  6:01               ` Jesper Nygårds

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=CABZhJg_4b6GiCo1J3BHzL0ACwao5Q_-HQgnhuHjQowUF+FVemQ@mail.gmail.com \
    --to=jesper.nygards@gmail.com \
    --cc=zsh-users@zsh.org \
    /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).