Re: [PATCH] Improve f=f interoperability

Hi, On Mon, Nov 05, 2007, Johannes Stezenbach wrote: > On Sun, Nov 04, 2007, Rocco Rutte wrote: > > * Johannes Stezenbach [07-11-04 12:43:00 +0100] wrote: > > > >> Have you made up your mind regarding this patch? It would > >> be nice if something like this would

Re: [PATCH] Improve f=f interoperability

Hi, (resend to the list, sorry for duplicate) On Sun, Nov 04, 2007, Rocco Rutte wrote: > * Johannes Stezenbach [07-11-04 12:43:00 +0100] wrote: > >> Have you made up your mind regarding this patch? It would >> be nice if something like this would be comitted before >&g

Re: [PATCH] Improve f=f interoperability (was: [PATCH] fix

Hi Rocco, On Tue, Oct 23, 2007, Rocco Rutte wrote: > * Johannes Stezenbach [07-10-19 14:39:48 +0200] wrote: >> On Thu, Oct 18, 2007, Rocco Rutte wrote: > >>>original: flowed? | reply: flowed? | trim spaces >>> 1 N N N >

Re: [PATCH] Improve f=f interoperability (was: [PATCH] fix

Hi, On Tue, Oct 23, 2007, Rocco Rutte wrote: >> On Thu, Oct 18, 2007, Rocco Rutte wrote: > >>>original: flowed? | reply: flowed? | trim spaces >>> 1 N N N >>> 2 N Y Y >>> 3 Y N

Re: [PATCH] fix indent_string handling with format=flowed

Hi, On Thu, Oct 18, 2007, Rocco Rutte wrote: > > Well, technically how mutt interprets the message is fully correct since > '>> >> foo' parses into quote depth 2 and content '>> Foo'. > > But I see your point and agree there's a problem and "format=flawed" is > true once more. If trimming spaces

Re: [PATCH] fix indent_string handling with format=flowed

Hi, On Tue, Oct 16, 2007, Rocco Rutte wrote: > > My main concern is still that in a discussion you'll loose all f=f benefits > if there's only one person doing a format=fixed reply that turns all flowed > into fixed lines. For example, in this discussion between us you would have > made message

Re: [PATCH] fix indent_string handling with format=flowed

Hi, On Tue, Oct 16, 2007, Rocco Rutte wrote: > * Johannes Stezenbach [07-10-15 23:46:23 +0200] wrote: > >> 2. reply to a format=fixed mail: just add '> ', not '>' >> (sub optimal but IMHO correct according to RFC 3676 -- since >> the lin

Re: [PATCH] fix indent_string handling with format=flowed

Hi again, On Mon, Oct 15, 2007, Rocco Rutte wrote: > * Johannes Stezenbach [07-10-14 21:54:36 +0200] wrote: >> At the moment, with $text_flowed set, replies to non-flowed mails >> get ugly quoting with '>' instead of '> '. Mutt _displays_ such >> qu

Re: [PATCH] fix indent_string handling with format=flowed

here I can disable all RFC 3676 processing and have mutt behave like a plain old MUA (this is for dealing with bad content created by other MUAs) - I do not want any "downgrade" or similar function On Mon, Oct 15, 2007, Rocco Rutte wrote: > * Johannes Stezenbach [07-10-14 21:12:59 +0

Re: [PATCH] fix indent_string handling with format=flowed

Hi, On Mon, Oct 15, 2007, Rocco Rutte wrote: > Ah, now I see your point. I fixed this in changeset 35e5c34b7e91 which also > fixes bug #2917. Thanks! It seems things get fixed in no time if we can agree on the problem :-) Johannes

Re: [PATCH] fix indent_string handling with format=flowed

Hi, On Sat, Oct 13, 2007, Rocco Rutte wrote: > * Johannes Stezenbach [07-10-12 23:14:21 +0200] wrote: >> On Thu, Oct 11, 2007, Rocco Rutte wrote: > >>> Mutt currently tries to keep interoperability by assuming that non-f=f >>> aware clients (including mutt itself wi

Re: [PATCH] fix indent_string handling with format=flowed

Hi, > * Johannes Stezenbach [07-10-12 23:14:21 +0200] wrote: >> I think it would be useful to have a config option to disable >> RFC 3676 handling of received messages altogether and make mutt >> behave like a plain old non-f=f aware MUA. > > Mutt with $text_flowed u

Re: [PATCH] fix indent_string handling with format=flowed

Hi, On Sat, Oct 13, 2007, Rocco Rutte wrote: > * Johannes Stezenbach [07-10-12 23:14:21 +0200] wrote: >> Just as I write this I notice another thing which might be a bug: >> According to RFC 3676 "4.1. Interpreting Format=Flowed": > >> A series of one or

Re: [PATCH] fix indent_string handling with format=flowed

Hi, I've taken some time to read RFC 3676 and conduct some experiments. Sorry for the long mail, the topic is tricky... On Thu, Oct 11, 2007, Rocco Rutte wrote: > * Johannes Stezenbach [07-10-10 20:49:38 +0200] wrote: > >> I think when the code which my patch changes is

Re: [PATCH] fix indent_string handling with format=flowed

Hi, On Wed, Oct 10, 2007 at 07:01:50PM +0200, Rocco Rutte wrote: > * Johannes Stezenbach [07-10-10 18:01:15 +0200] wrote: > >> changeset: 5109:d3e0d6c60d87 >> branch: HEAD >> user:Brendan Cully <[EMAIL PROTECTED]> >> date:Tue Apr 10 13:46

[PATCH] fix indent_string handling with format=flowed

Hi, changeset: 5109:d3e0d6c60d87 branch: HEAD user:Brendan Cully <[EMAIL PROTECTED]> date:Tue Apr 10 13:46:09 2007 -0700 summary: Don't use $indent_string to quote replies to flowed messages (closes #2874). introduced a regression when replying to format=flowed mails.