From: Peter Stephenson <p.stephenson@samsung.com>
To: Danielle McLean <gopsychonauts@gmail.com>, zsh-workers@zsh.org
Cc: danielsh@apache.org
Subject: Re: zsh/complist colours improperly handle multibyte characters
Date: Fri, 21 Oct 2016 09:33:55 +0100 [thread overview]
Message-ID: <20161021093355.2fc2058b@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <etPan.58096283.690aeb81.31f@dani-mac.newcastle.edu.au>
On Fri, 21 Oct 2016 12:09:34 +1100
Danielle McLean <gopsychonauts@gmail.com> wrote:
> Although zsh patterns usually have full support for multibyte
> characters, a zsh pattern containing certain multibyte characters will
> fail to match if provided to zsh/complist using $ZLS_COLORS or the
> list-colors zstyle.
Yes, unfortunately character-by-character analysis is built into
completion at quite a low level.
I don't know a great deal about the complist code --- except it's
appeared utterly opaque when I have looked at it --- but I did
try to get grips with the matching control, where there are similar
problems, and utterly failed. The assumption that a byte in the
string on the command line and a byte in the test string can be
considered equivalent is all-pervasive, but the sort of tricks in use
didn't make converting to wide characters a particularly attractive
optin, either. It became clear this was a huge job I didn't have a clue
about.
complist may not be quite that bad, and indeed character *matching*
isn't a big part of it so this may not be a particularly difficult
problem when it comes down to it, but unless anyone makes it their
life's work to get to grips with it it's probably stuck --- it's clear
Bart and I aren't ever going to have that sort of time.
pws
next prev parent reply other threads:[~2016-10-21 8:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161021011017eucas1p1d1fceae920242e69b4426bc41cb3c064@eucas1p1.samsung.com>
2016-10-21 1:09 ` Danielle McLean
2016-10-21 4:07 ` Bart Schaefer
2016-10-23 17:30 ` Peter Stephenson
2016-10-23 18:23 ` Bart Schaefer
[not found] ` <20161023184641.4549e10a@ntlworld.com>
[not found] ` <161023105652.ZM3309@torch.brasslantern.com>
2016-10-23 18:59 ` Peter Stephenson
2016-10-23 19:34 ` Bart Schaefer
2016-10-25 10:44 ` Peter Stephenson
2016-10-25 15:59 ` Bart Schaefer
2016-10-25 16:05 ` Peter Stephenson
2016-10-21 8:33 ` Peter Stephenson [this message]
2016-10-21 15:48 ` 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=20161021093355.2fc2058b@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.com \
--cc=danielsh@apache.org \
--cc=gopsychonauts@gmail.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).