From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: 3.1.6-test-3: BUG: accept-and-menu-complete in menuselect
Date: Thu, 29 Jul 1999 16:40:20 +0400 [thread overview]
Message-ID: <001101bed9bf$84f3be60$21c9ca95@mow.siemens.ru> (raw)
bor@itsrm2:/tools/src%> l vim<TAB><TAB>
bor@itsrm2:/tools/src%> l vim-5.4
vim-5.4/ vim-5.4l/ vim-5.4m/ vim-5.4n/
(with proper highlighting etc)
accept-and-menu-complete (ESC-RETURN in my case)
bor@itsrm2:/tools/src%> l vim-5.4^@vim-5.4l/
vim-5.4/ vim-5.4l/ vim-5.4m/ vim-5.4n/
once more
bor@itsrm2:/tools/src%> l vim-5.4^@vim-5.4l/Vim-5.4m/
vim-5.4/ vim-5.4l/ vim-5.4m/ vim-5.4n/
Note capitalised ``V'' the second time!!!
3.1.6-test-3 pure
/andrej
next reply other threads:[~1999-07-29 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-29 12:40 Andrej Borsenkow [this message]
1999-07-29 12:17 ` Peter Stephenson
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='001101bed9bf$84f3be60$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--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).