From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: _files -g and subdirectory completion
Date: Mon, 28 Feb 2000 12:53:50 +0100 (MET) [thread overview]
Message-ID: <200002281153.MAA03235@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Alexandre Duret-Lutz's message of 28 Feb 2000 12:02:18 +0100
Alexandre Duret-Lutz wrote:
> What's happening with _files -g ? I am missing a new style ?
>
> ~/tmp/m1 % zsh -f
> phobos% autoload -U compinit
> phobos% compinit
> phobos% mkdir -p foo/bar
> phobos% zcat foo/<TAB>
>
> Nothing complete. It behaves like this with all completions
> functions using _files -g.
Yep. That break in _path_files already irritated me some time
ago. Let's try without it...
I'm awfully sorry about all this mess with file completion. Sigh.
Bye
Sven
diff -ru ../z.old/Completion/Core/_path_files Completion/Core/_path_files
--- ../z.old/Completion/Core/_path_files Mon Feb 28 12:01:23 2000
+++ Completion/Core/_path_files Mon Feb 28 12:52:20 2000
@@ -346,9 +346,13 @@
# if none of the patterns match.
if [[ -z "$tpre$tsuf" && -n "$pre$suf" ]]; then
- tmp1=( "$tmp2[@]" )
pfxsfx=(-S '' "$pfxsfx[@]")
- break
+ ### Don't remember what the break was good for. We explicitly
+ ### execute this only when there are no matches in the directory,
+ ### so why continue?
+ ###
+ ### tmp1=( "$tmp2[@]" )
+ ### break
elif [[ "$haspats" = no && -z "$tpre$tsuf" &&
"$pre" = */ && -z "$suf" ]]; then
PREFIX="${opre}"
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-02-28 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-28 11:53 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-02-28 11:02 Alexandre Duret-Lutz
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=200002281153.MAA03235@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.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).