From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: expand style `suffix' option
Date: Tue, 2 Oct 2001 14:52:08 +0000 [thread overview]
Message-ID: <1011002145208.ZM24576@candle.brasslantern.com> (raw)
In-Reply-To: <22658.1002022881@csr.com>
On Oct 2, 12:41pm, Peter Stephenson wrote:
}
} zstyle ':completion:*' expand prefix suffix
}
} When it does seem to be on, I would expect
} ~/b/b<TAB>
} to list or cycle through all files ~/b*/b* when menu completion is in use,
} but it doesn't. Is this assumption wrong?
I get the exact same behavior out of that no matter what `expand' is set
to. E.g. I happen to have two files
~/netmanage/record
~/newmail/record
but no matter what the setting of the expand style, I always get:
schaefer<512> ls ~/n/r<TAB>
schaefer<512> ls ~/ne/r
(with cursor on the second `/'). Using menucomplete instead of automenu,
I get the menu:
schaefer<514> ls ~/n/r<TAB>
schaefer<515> ls ~/netmanage/r
Completing files
netmanage/ newmail/
but once again the `expand' style has no effect on this.
It looks like _path_files applies the `expand prefix' style only if the
number of matches generated is the same as the number that existed at
the time _path_files was called (line 655, nm -eq compstate[nmatches]).
But that never seems to be true.
Also, _path_files only checks that `expand suffix' is NOT set, and then
as part of a larger test to decide whether to clear compstate[to_end]
(lines 508-515), and I can't figure out what circumstances cause all the
other ||'d conditions to be false so that `expand suffix' will matter.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-10-02 14:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-02 11:41 Peter Stephenson
2001-10-02 14:52 ` Bart Schaefer [this message]
2001-10-04 13:10 ` Sven Wischnowsky
2001-10-04 13:33 ` Peter Stephenson
2001-10-05 11:17 ` Sven Wischnowsky
2001-10-05 16:10 ` PATCH: " Peter Stephenson
2001-10-08 12:33 ` Sven Wischnowsky
2001-10-09 9:48 ` Sven Wischnowsky
2001-10-09 10:35 ` 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=1011002145208.ZM24576@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.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).