From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "Andrei Rybak" <rybak.a.v@gmail.com>,
git@vger.kernel.org, "SZEDER Gábor" <szeder.dev@gmail.com>,
"Duy Nguyen" <pclouds@gmail.com>
Subject: Re: [PATCH v2 2/2] mailinfo: support Unicode scissors
Date: Wed, 03 Apr 2019 15:47:47 +0900 [thread overview]
Message-ID: <xmqq8swrtwj0.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20190402143615.GC10564@sigill.intra.peff.net> (Jeff King's message of "Tue, 2 Apr 2019 10:36:15 -0400")
Jeff King <peff@peff.net> writes:
> In fact, I think you could then combine this with the previous
> conditional and get:
>
> if (skip_prefix(c, ">8", &end) ||
> skip_prefix(c, "8<", &end) ||
> skip_prefix(c, ">%", &end) ||
> skip_prefix(c, "%<", &end) ||
> /* U-2702 in UTF-8 */
> skip_prefix(c, "\xE2\x9C\x82", &end)) {
> in_perforation = 1;
> perforation += end - c;
> scissors += end - c;
> c = end - 1; /* minus one to account for loop increment */
> }
>
> (Though I'm still on the fence regarding the whole idea, so do not take
> this as an endorsement ;) ).
I do not think we want to add more, but use of skip_prefix does
sound sensible. I was very tempted to suggest
static const char *scissors[] = {
">8", "8<", ">%", "%<",
NULL,
};
const char **s;
for (s = scissors; *s; s++)
if (skip_prefix, c, *s, &end) {
in_perforation = 1;
...
break;
}
}
if (!s)
... we are not looking at any of the scissors[] ...
but that would encourage adding more random entries to the array,
which we would want to avoid in order to help reduce the cognirive
load of end-users.
In hindsight, addition of an undocumented '%' was already a mistake.
I wonder how widely it is in use (yes, I am tempted to deprecate and
remove these two to match the code to the docs).
next prev parent reply other threads:[~2019-04-03 6:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-31 22:01 [PATCH] mailinfo: support Unicode scissors Andrei Rybak
2019-03-31 23:09 ` SZEDER Gábor
2019-04-01 9:07 ` Junio C Hamano
2019-04-01 10:11 ` Jeff King
2019-04-01 9:27 ` Duy Nguyen
2019-04-01 21:54 ` Andrei Rybak
2019-04-01 21:53 ` [PATCH v2 1/2] mailinfo: use starts_with() for clarity Andrei Rybak
2019-04-01 21:53 ` [PATCH v2 2/2] mailinfo: support Unicode scissors Andrei Rybak
2019-04-02 14:36 ` Jeff King
2019-04-03 6:47 ` Junio C Hamano [this message]
2019-04-02 14:28 ` [PATCH v2 1/2] mailinfo: use starts_with() for clarity Jeff King
2021-06-08 20:48 ` [PATCH] mailinfo: use starts_with() when checking scissors Andrei Rybak
2021-06-08 21:57 ` Jeff King
2021-06-09 2:22 ` Junio C Hamano
2021-06-09 3:59 ` Jeff King
2021-06-09 5:11 ` Junio C Hamano
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=xmqq8swrtwj0.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=rybak.a.v@gmail.com \
--cc=szeder.dev@gmail.com \
/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.
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).