From: Andy Spiegl <zsh.Andy@spiegl.de>
To: zsh-users@sunsite.dk
Subject: Re: howto expand all possible completions?
Date: Sat, 24 Jun 2006 22:57:11 +0200 [thread overview]
Message-ID: <20060624205711.GA29371@spiegl.de> (raw)
In-Reply-To: <060623201956.ZM6283@torch.brasslantern.com>
Hi Bart,
> } Is there something like expand-completions or similar?
>
> Do you already have _expand in your completers style?
No, thanks for the hint!
Hm, the description of the function sounds great but I don't understand how
it's supposed to work. I've got TAB bound to complete-word and now use:
zstyle ':completion:*' completer _expand _expand_dots _complete _match _correct _7slash
but the behavior is still the same: when I press TAB I get to see all the
possible completions but they don't get written to the command line.
Do I need any other style definitions?
> If so, my only other suggestion would be to try setopt nocaseglob. I
> suspect that you have a lower-case to upper-case matcher-list style
> that is producing the mixed-case completions in the second example.
Correct. nocaseglob would help in this example of mine but there are many
different cases where the completer shows all kinds of different types of
possible completions, e.g. the "partial match" style:
zstyle ':completion:*' matcher-list 'm:{A-Zöäüa-zÖÄÜ}={a-zÖÄÜA-Zöäü} m:[-_]=[-_] r:|[-./_]=** r:|=*' '+l:|=*'
which gives:
condor:~/pic/Nature>qiv ham<TAB>
- files -
A-Caribbean-reef-shark-swims-over-a-coral-reef-in-the-Bahamas.jpg cham1024.jpg cyclonegraham.jpg
I tried calling the _expand function manually (via Alt-x) but that just
hogged the CPU so that I had to kill zsh. :-(
Thanks,
Andy.
--
Isn't making a smoking section in a restaurant
like making a peeing section in a swimming pool? (George Carlin, US comedian)
next prev parent reply other threads:[~2006-06-24 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 23:29 Andy Spiegl
2006-06-24 3:19 ` Bart Schaefer
2006-06-24 20:57 ` Andy Spiegl [this message]
2006-06-25 3:04 ` Bart Schaefer
2006-06-25 19:17 ` Andy Spiegl
2006-06-25 19:37 ` Bart Schaefer
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=20060624205711.GA29371@spiegl.de \
--to=zsh.andy@spiegl.de \
--cc=zsh-users@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).