zsh-users
 help / color / mirror / code / Atom feed
From: Yuri DElia <wavexx@users.sf.net>
To: zsh-users@zsh.org
Subject: Re: Completion lists
Date: Tue, 13 Sep 2011 15:16:12 +0000 (UTC)	[thread overview]
Message-ID: <loom.20110913T170627-86@post.gmane.org> (raw)
In-Reply-To: <110913074320.ZM14249@torch.brasslantern.com>

Bart Schaefer <schaefer <at> brasslantern.com> writes:

> zstyle -e ':completion:*:default' list-colors \
>     'reply=("=(#b)${words[CURRENT]:t}(*)=0=7")'
> 
> The -e option evaluates the style so you can use $words[CURRENT] to put
> the string from the line into the style.  The highlight is controlled
> by the =0=3 part, where =0 means no highlight on the parts that are
> not matched by a pattern in parens and the =7 means use reverse video
> on the part matched by the first sub-pattern in parens (here "(*)").
> See the doc for the complist module ZLS_COLORS variable.

Your code seem to fail badly with directories.
For instance, completing anything with "./" will incorrectly skip the first two
characters of the files themselves.

> If you've got matcher-list styles that do fancy completion in the middle
> of words, $words[CURRENT] is going to be inadequate to the task (and it
> is likely that nothing you can expand at the time the list-colors style
> is evaluated would be sufficient).  You might specify case-insensitive
> globbing on to help with mixed-case matcher-lists:
> 
> zstyle -e ':completion:*:default' list-colors \
>     'reply=("=(#bi)${words[CURRENT]:t}(*)=0=7")'

While I was waiting I kept trying and came up with this:

c='${PREFIX:+=(#b)($PREFIX:t)(?)*===$color[bold]}':'=(#b)(?)*==$color[bold]'
zstyle -e ':completion:*' list-colors "reply=(\"$c\")"

The first part of the reply matches the first character after the prefix.
The second matches the first character in a list (when completing directories). 
Seems to work fine for both files and parameters.

Doesn't work for anything beyond prefix matching:

$ ls ///list<TAB> (ambiguous)
etc/
lib/
usr/

will simply put the cursor after the first / and highlight the third characters 
of the list (and I don't understand why).

I'm wondering what variables could in the reply. I found $PREFIX in other 
examples, and now also $words[CURRENT]. Is there a list for these? Maybe I 
could make it work if I had SUFFIX/somethingelse.

> If someone builds up a useful set of these based on this example, please
> post back to the list.

I would also be glad.



  reply	other threads:[~2011-09-13 15:16 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 [this message]
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
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.20110913T170627-86@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).