From: Tomi Ollila <tomi.ollila@iki.fi>
To: David Edmondson <dme@dme.org>, notmuch@notmuchmail.org
Subject: Re: [BUG] notmuch-emacs highlights '>' quoted wrapped lines incorrectly
Date: Fri, 06 Jan 2017 13:26:31 +0200 [thread overview]
Message-ID: <m2k2a88m54.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <m260lseaaf.fsf@dme.org>
On Fri, Jan 06 2017, David Edmondson <dme@dme.org> wrote:
> On Fri, Jan 06 2017, Tomi Ollila wrote:
>
>> On Thu, Jan 05 2017, David Edmondson <dme@dme.org> wrote:
>>
>>> On Thu, Jan 05 2017, Jani Nikula wrote:
>>>
>>>> When the show view in notmuch-emacs highlights quoted text, any long,
>>>> folded lines in quotes prefixed using '>' fail to be highlighted. Quotes
>>>> prefixed using '> ' work fine. See below.
>>>
>>> Maybe fiddle with `coolj-line-prefix-regexp', which is "^\\(>+ \\)*" by
>>> default (note the space).
>>>
>>> "^\\(>+ ?\\)*" gets it working, but I didn't think through all of the
>>> consequences.
>>
>> How does that behave different than "^\\(>+\\)*" (quick thougth (also))?
>
> The first matches all of "> > " (which I receive sometimes), the latter
> doesn't.
Ah ok, now I understand: coolj when wrapping lines, adds the matched part
to the beginning of lines (match may be empty due to *, meaning not
prefixing line with anything). I don't see any consequences so far.
Tomi
PS: "^\\(>+ *\\)*" could also be an option but perhaps we could start
with your suggestion before breaking thing even more >;)
next prev parent reply other threads:[~2017-01-06 11:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 18:48 [BUG] notmuch-emacs highlights '>' quoted wrapped lines incorrectly Jani Nikula
2017-01-05 19:01 ` David Edmondson
2017-01-06 10:30 ` Tomi Ollila
2017-01-06 10:46 ` David Edmondson
2017-01-06 11:26 ` Tomi Ollila [this message]
2021-12-25 23:31 ` [PATCH] emacs: update coolj-line-prefix-regexp to make space optional David Bremner
2021-12-29 17:47 ` Tomi Ollila
2021-12-29 18:26 ` David Bremner
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2k2a88m54.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=dme@dme.org \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).