zsh-users
 help / color / mirror / code / Atom feed
From: DervishD <raul@pleyades.net>
To: zsh-users@sunsite.dk
Subject: Re: Coloring completions
Date: Thu, 15 Jul 2004 18:36:43 +0200	[thread overview]
Message-ID: <20040715163643.GA10866@DervishD> (raw)
In-Reply-To: <Pine.LNX.4.60.0407150813040.28477@toltec.zanshin.com>

    Hi Bart :)

 * Bart Schaefer <schaefer@brasslantern.com> dixit:
> >     Hey, that's weird :((( I'm testing again completion and *all*
> > colorable files are colored *except* directories
> unsetopt markdirs

    Oh, my... Thanks, Bart, you're great :)
 
> When markdirs is set, the expansion of the glob appends a trailing slash 
> to the file name, and thus the coloring code no longer recognizes it as
> being a string match for the actual directory name.

    Why it doesn't happen with executable names (which has an
asterisk added) or other kind of files? I mean, why 'listtypes'
doesn't have the same effect?

> (When you're using default completion the file expansion is all done in 
> the internals and markdirs is ignored.)

    But the same is not applicable to 'listtypes'. Doesn't seem that
weird?
 
> You might want to take a look at the value assigned to the _comp_options
> array in compinit, and the subsequent _comp_setup assignment.  One of
> the first things _main_complete does is to eval that setup string.

    Yes, I've took a look at it: very clever and useful :)) Thanks a
lot, Bart, as always :)

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/


  reply	other threads:[~2004-07-15 17:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-14 11:21 DervishD
2004-07-15  3:27 ` Bart Schaefer
2004-07-15 10:50   ` DervishD
2004-07-15 15:21     ` Bart Schaefer
2004-07-15 16:36       ` DervishD [this message]
2004-07-16  2:20         ` Bart Schaefer
2004-07-16  8:20           ` DervishD
2005-11-21 13:18 Nikolai Weibull
     [not found] ` <200511211902.46023.arvidjaar@mail.ru>
2005-11-21 16:12   ` Nikolai Weibull

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=20040715163643.GA10866@DervishD \
    --to=raul@pleyades.net \
    --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).