From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: "ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: _match and auto menu with multipath again
Date: Tue, 15 Jun 1999 17:05:21 +0400 [thread overview]
Message-ID: <002b01beb72f$b93bc300$21c9ca95@mow.siemens.ru> (raw)
As I can recall, _match automatically starts menu completion (if more than one
choice is present). I won't argue that (after all, there is no place where I can
type in next char :-), but I still find the current way pretty confusing:
bor@itsrm2:~%> compconf -L
compconf correct_accept='2n'
compconf match_original='yes'
compconf completer='_complete:_match'
compconf dumpfile='/home/bor/.zcompdump'
compconf correct_prompt='correct to:'
bor@itsrm2:~%> l /a/p/u/z/z*22*<TAB>
bor@itsrm2:~%> l /archive/pub/unix/zip/z*22*
zip/ zsh/
Note again, that menu is started for some middle path - without *any* visible
feedback for user (that is, I have no idea what is being completed). Even worse,
repeatedly typing TAB cycles through ``zip'' and ``zsh'', leaving no way to
select one (yes, I know - 'cursor-left,cursor-right' etc, but they are not
*natural* way). This switch to menu is very unexpected and will confuse many
users.
That was mostly a reason, why I requested cursor be placed on a word part that
is being completed. How hard is it to simply start normal completion? What I
mean, is:
bor@itsrm2:~%> l /a/p/u/z/z*22*<TAB>
bor@itsrm2:~%> l /archive/pub/unix/z/z*22*
zip/ zsh/ ^ cursor here
and after this part is done, simply start normal completion for the next
ambiguous part?
I don't insist on it being default, but as an option?
/andrej
next reply other threads:[~1999-06-16 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-15 13:05 Andrej Borsenkow [this message]
1999-06-17 8:37 Sven Wischnowsky
1999-06-17 9:27 ` Andrej Borsenkow
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='002b01beb72f$b93bc300$21c9ca95@mow.siemens.ru' \
--to=borsenkow.msk@sni.de \
--cc=zsh-workers@sunsite.auc.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).