From: Yuri DElia <wavexx@users.sf.net>
To: zsh-users@zsh.org
Subject: Re: Completion lists
Date: Tue, 13 Sep 2011 17:11:54 +0000 (UTC) [thread overview]
Message-ID: <loom.20110913T185808-173@post.gmane.org> (raw)
In-Reply-To: <110913092957.ZM14421@torch.brasslantern.com>
Bart Schaefer <schaefer <at> brasslantern.com> writes:
> Strictly speaking I think you should use =0=0=$color[bold]}, that may be
> why strange things are getting highlighted in some of your attempts. I
> get different results with =0=0= vs ===.
Doesn't do anything for me.
Could you please try the following?
highlights='${PREFIX:+=(#b)${PREFIX:q:t}(?)*=0=1}':'=(#b)(?)*=0=1'
zstyle -e ':completion:*' list-colors "reply=(\"$highlights\")"
unset highlights
and try
touch filea
touch fileb
ls ./<TAB>
ls ./file<TAB>
ls ./<TAB>
and report what happens?
In the first ls, the first character is highlighted. In the second, [ab] should
be highlighted. In the third, the '=(#b)(?)*=0=1' expression fails, and matches
[ab] instead of [f].
You can also try this afterwards:
highlights='=(#b)(?)*=0=1'
zstyle -e ':completion:*' list-colors "reply=(\"$highlights\")"
unset highlights
and it will still match [ab].
Can you replicate this issue?
next prev parent reply other threads:[~2011-09-13 17:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 12:54 Yuri DElia
2011-09-13 14:43 ` Bart Schaefer
2011-09-13 15:16 ` Yuri DElia
2011-09-13 16:07 ` Yuri DElia
2011-09-13 17:40 ` Bart Schaefer
2011-09-13 18:48 ` Yuri DElia
2011-09-16 21:04 ` Peter Stephenson
2011-09-16 21:07 ` Peter Stephenson
2011-09-13 16:29 ` Bart Schaefer
2011-09-13 17:11 ` Yuri DElia [this message]
2011-09-18 13:41 ` Yuri DElia
2011-09-18 13:48 ` Mikael Magnusson
[not found] ` <ed790212f803298ea33fd6091b9d5062@thregr.org>
2011-09-18 14:08 ` Mikael Magnusson
2011-09-18 14:35 ` Yuri D'Elia
2011-09-16 21:58 ` Tomasz Pala
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=loom.20110913T185808-173@post.gmane.org \
--to=wavexx@users.sf.net \
--cc=zsh-users@zsh.org \
/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).