zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-workers@math.gatech.edu
Subject: REC_EXACT and AUTO_MENU, and compctl -U too
Date: Fri, 19 Jun 1998 11:14:59 -0700	[thread overview]
Message-ID: <980619111459.ZM9964@candle.brasslantern.com> (raw)

One thing that's annoyed me for a very long time is the interaction of
recexact with automenu.  Suppose I have both options set.

zsh% /usr/li

The possible completions at this point are /usr/lib and /usr/libexec.  I
press TAB (which is bound to expand-or-complete).

zsh% /usr/lib

This is not a completion; it's the unique prefix of a menu completion, or
it would be in most circumstances.  With recexact, though, when I press
TAB again expecting to menucomplete to libexec, I instead get /usr/lib/
and now I can only complete within that directory.

What I'd like is to have recexact behavior when I type the entire prefix
and automenu behavior when zsh supplies the prefix.

While I'm on the subject of mildly stupid completion behavior, automenu
in conjunction with compctl -U could do with a bit of work.  It'd be a
lot more useful if menu completion kicked in immediately when compctl -U
returns multiple matches and automenu is set.  Otherwise you lose both
the set of completions and the nonunique suffix as soon as the first TAB
is pressed.

I haven't dug around in the code for either of these yet; any conflicting
opinions on whether this is worthwhile?  Any remarks on how difficult they
are to pull off?

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


             reply	other threads:[~1998-06-19 18:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-06-19 18:14 Bart Schaefer [this message]
1998-06-19 18:53 ` Zefram
1998-06-19 19:28   ` Bart Schaefer

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=980619111459.ZM9964@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@math.gatech.edu \
    /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).