From: Peter Stephenson <p.stephenson@samsung.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: [BUG] SIGSEGV under certain circumstances
Date: Mon, 06 Mar 2017 09:47:44 +0000 [thread overview]
Message-ID: <20170306094744.290c1fbd@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <170305134513.ZM26364@torch.brasslantern.com>
On Sun, 5 Mar 2017 13:45:13 -0800
Bart Schaefer <schaefer@brasslantern.com> wrote:
> [Somebody will have to explain to me why (mp += cl) makes sense, as that
> seems to be using a byte count to increment a (Cmatcher*), but it's done
> in several places.]
We're getting down to the point where the matcher hasn't been fully
converted to multibyte chracters (though I can't swear this is it), and
indeed right at the bottom I seem to remember it uses arrays to such an
extent it would be more natural to use wide characters. But that turned
out to be easier said than done too --- partly I think it was a question
of being able to store pattern characters.
> Am I going astray here?
I don't understand your point since the functions being called here are
all adapted for metafied multibyte characters, but I'm obviously missing
something.
pws
next prev parent reply other threads:[~2017-03-06 9:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 15:38 Chi-Hsuan Yen
2017-03-04 23:11 ` Bart Schaefer
2017-03-05 12:55 ` Chi-Hsuan Yen
2017-03-05 13:09 ` Chi-Hsuan Yen
2017-03-05 16:00 ` Bart Schaefer
2017-03-05 16:17 ` Peter Stephenson
2017-03-05 18:42 ` Bart Schaefer
2017-03-05 18:52 ` Peter Stephenson
2017-03-05 21:45 ` Bart Schaefer
2017-03-05 22:31 ` Bart Schaefer
2017-03-05 22:41 ` Daniel Shahaf
2017-03-05 22:51 ` Bart Schaefer
2017-03-05 23:07 ` Bart Schaefer
2017-03-06 0:23 ` Bart Schaefer
2017-03-06 9:47 ` Peter Stephenson [this message]
2017-03-06 17:10 ` 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=20170306094744.290c1fbd@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.com \
--cc=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).