From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.dk
Subject: Re: expand style `suffix' option
Date: Thu, 4 Oct 2001 15:10:07 +0200 [thread overview]
Message-ID: <15292.24495.82880.514083@gargle.gargle.HOWL> (raw)
In-Reply-To: <22658.1002022881@csr.com>
Peter Stephenson wrote:
> ...
>
> First off, I assumed I could do
> zstyle ':completion:*' expand 'prefix suffix'
> but a look at the code reveals this has to be
> zstyle ':completion:*' expand prefix suffix
> so `contains the string' could be made a little clearer.
Yes.
> 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.
Well, it says (or tries to say) that this suff-behaviour is only done
when not using menu-completion. I think we either had a discussion or
I thought that people using menu-completion wouldn't want to be
bothered with looong lists.
But anyway, that style appears to be broken (both prefix and
suffix). I seem to have a fix for the suffix thing now (it was broken
when list-suffixes was added, I think) and I know what's the problem
for the prefix part (compfiles building the pattern, so that
_path_files doesn't have the original anymore and doesn't add it to
$exppaths). I'll look into this tomorrow or next week.
Restoring those things would still not make it work with menu
completion, though (the suffix thing), but that could be added. Should
we?
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next prev parent reply other threads:[~2001-10-04 13:10 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
2001-10-04 13:10 ` Sven Wischnowsky [this message]
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=15292.24495.82880.514083@gargle.gargle.HOWL \
--to=wischnow@informatik.hu-berlin.de \
--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).