From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 40951@debbugs.gnu.org
Subject: bug#40951: Weird highlighting
Date: Wed, 29 Apr 2020 09:44:56 +0200 [thread overview]
Message-ID: <87tv12ohvr.fsf@gmail.com> (raw)
In-Reply-To: <87imhj6rl6.8.fsf@jidanni.org> ("積丹尼 Dan Jacobson"'s message of "Wed, 29 Apr 2020 08:52:37 +0800")
積丹尼 Dan Jacobson <jidanni@jidanni.org> writes:
> Why does the
> taking...:
> line get different color (bad)
> but the
> A couple...:
> line not? (good).
> [pipe to procmail:]
>
> From: Martin Ward <martin@gkc.org.uk>
> Subject: Re: How NASA does software testing and QA (Functionize)
> Date: Tue, 28 Apr 2020 17:05:17 +0800 (22 hours, 29 minutes, 33 seconds ago)
>
> Crumbley does not say what level NASA's software development department has
> currently reached, or what level they are aiming at nor what steps they are
> taking to reach the desired level. Instead he says:
>
> No such bug when viewed in mutt.
>
> Gnus v5.13
I'd blame gnus-cite-attribution-suffix. Try setting it to a regexp that
doesn't match "says:", then redisplay the article with 'g'.
That sounds like a tricky bug to fix. On the one hand, I've seen many
false positives (i.e. lines highlighted because someone writes e.g. "the
manual/docstring/comment says:"), on the other hand I don't see how Gnus
could distinguish between a verb added deliberately by the article
author, and the same verb added automatically as part of the mail
client's citation boilerplate.
next prev parent reply other threads:[~2020-04-29 7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 0:52 bug#40951: Weird highlighting 積丹尼 Dan Jacobson
2020-04-29 7:44 ` Kévin Le Gouguec [this message]
2020-04-29 17:50 ` 積丹尼 Dan Jacobson
2020-05-01 18:44 ` Kévin Le Gouguec
2020-08-05 11:19 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tv12ohvr.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=40951@debbugs.gnu.org \
--cc=jidanni@jidanni.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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).