On Fri, Dec 11, 2015 at 09:46:32AM +0100, Fabian Groffen wrote:
> On 10-12-2015 15:37:29 -0800, Kevin J. McCarthy wrote:
> >     >>>foo       >>>>foo          >>>>>>foo
> 
> This is a bug (the same happens below, snipped for brevity).

> I think what the Gentoo patch tries to achieve is to keep consistent
> quotation (> > > vs > >>, but also | | vs | > or > |), plus the
> preference of some people to not quote empty lines at all.

Ah... thank you for the clear explanation.  I got caught up in the
details and my mind couldn't figure out what the purpose of the patches
was.

> > Even if this made any sense, both patches override reflow_text when
> > replying, and the FreeBSD patch uses a fixed buffer size, making them
> > unsuitable for just applying.
> 
> I see how this is undesired.  Am I correct if I think it needs some
> function that does the quotation-prefix mangling which then can be
> called from both the text_plain_handler and rfc3676_handler?

I think the right approach would be to hook into both handlers.

However, if you are in rfc3676_handler, you already know what the quote
character is, so I don't think it needs to call the same function as
text_plain_handler.  In indent_handler(), you could just have something
like
    if (option (OPTTEXTFLOWED) || option (OPTQUOTEQUOTED))
          ql++;

The only issue is the email I just sent replying to Will - we may
end up tweeking rfc3676_handler to allow the quote spacing to be
toggled.

-- 
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA
http://www.8t8.us/configs/gpg-key-transition-statement.txt

Attachment: signature.asc
Description: PGP signature

Reply via email to