zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh Workers <zsh-workers@zsh.org>
Subject: Re: ( Text in unknown character set UTF-8 not shown )
Date: Sat, 13 Nov 2010 07:53:31 -0800	[thread overview]
Message-ID: <101113075331.ZM15942@torch.brasslantern.com> (raw)
In-Reply-To: <AANLkTikt-ZdJA_+hSLEc88+Qu2a8a4GJiGRW5RQHM2HK@mail.gmail.com>

On Nov 13,  4:07pm, Nikolai Weibull wrote:
}
} _multi_parts -f doesn't seem to have any effect.  At least note the
} one I care about, which is to apply colors to different file types.
} Is this a known issue?

It defintely passes -f through to compadd, so you're going to have to
be a bit more specific.  However, there are likely to be two combined
effects at work here.

(1) File type coloring is applied only to files that can be examined
with stat(2), unless you have some pattern-match colorings defined.

(2) _multi_parts treats each "component" of the string it breaks up as
an independent match, so it passes the prefix from the line to compadd
using -P rather than -W.

The result is that _multi_parts can only apply file coloring in cases
where there is no path prefix, i.e., files in the current directory.

Which, IIRC, is why _path_files exists in the first place.


  reply	other threads:[~2010-11-13 15:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-13 15:07 _multi_parts -f doesn’t seem to have any effect Nikolai Weibull
2010-11-13 15:53 ` Bart Schaefer [this message]
2010-11-13 16:09   ` _multi_parts -f doesn't " Bart Schaefer
     [not found] <AANLkTi=vnaRw3qxpuuEWF9t0K-TyPJKkhVUYy_8qR-=e@mail.gmail.com>
     [not found] ` <101222231721.ZM21959@torch.brasslantern.com>
2010-12-23 17:41   ` ( Text in unknown character set UTF-8 not shown ) ZyX

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=101113075331.ZM15942@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@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).