From: Tanaka Akira <akr@jaist.ac.jp>
To: zsh-workers@sunsite.auc.dk
Subject: _files does not list files after foo/
Date: 25 Jul 1999 01:29:38 +0900 [thread overview]
Message-ID: <rsq673aj9jh.fsf@crane.jaist.ac.jp> (raw)
Z(2):akr@is27e1u11% zsh -f
is27e1u11% autoload -U compinit; compinit -D
is27e1u11% ls
ChangeLog Doc META-FAQ README acconfig.h config.guess config.status install-sh
ChangeLog.3.0 Etc Makefile Src aclocal.m4 config.h config.sub mkinstalldirs
Completion Functions Makefile.in StartupFiles aczsh.m4 config.h.in configure stamp-h
Config INSTALL Misc Util config.cache config.log configure.in stamp-h.in
is27e1u11% gunzip ./<TAB>
After above operation, zsh does not list files in current directory.
OK, I know that the behaviour is intentional as:
_path_files:
| # A little extra hack: if we were completing `foo/<TAB>' and `foo'
| # contains no files, this will normally produce no matches and other
| # completers might think that's it's their time now. But if the next
| # completer is _correct or something like that, this will result in
| # an attempt to correct a valid directory name. So we just add the
| # original string in such a case so that the command line doesn't
| # change but other completers still think there are matches.
|
| if [[ -z "$tpre$tsuf" && "$pre" = */ && -z "$suf" ]]; then
| compadd -nQS '' - "$linepath$donepath$orig"
| tmp4=-
| fi
But it is confusing in this case.
I suppose that there should be the way to disable the hack.
--
Tanaka Akira
next reply other threads:[~1999-07-24 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-24 16:29 Tanaka Akira [this message]
1999-07-27 14:07 ` Peter Stephenson
1999-08-02 13:40 Sven Wischnowsky
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=rsq673aj9jh.fsf@crane.jaist.ac.jp \
--to=akr@jaist.ac.jp \
--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).