Subject: Problems with flowed text

From: Chris Wilson <[email-masked]>
Date: Sun, 13 Feb 2005 18:19:53 +0000 (GMT)

Dear Sirs,

I think I have found a bug with Pine's flowed text feature, where it 
interacts badly with code-style indentations. The indents below will 
probably not appear if you run Pine 4.61 (as I do).

      four spaces: flghk;lgkh; fgfg hl gf h;gk hl;fhk gf h;gkh ;fg
      gfljh;ko5rt p'ert;o troktg fo thkfotkh;k;lvghk ;f

         eight spaces: d;fg krt;gk ptotpo t;fh ltrhjxijhweizfugurg g er
         idur dh igh hgu hiudhguihrdghidxg

         one tab: d;fg krt;gk ptotpo t;fh ltrhjxijhweizfugurg g er idur dh
         igh hgu hiudhguihrdghidxg

However, if you turn headers on, or view the message as an attachment, the 
indentations appear fine.

I'm assuming that this is not fixed in release 4.62, since I can't see any 
mention of it in the release notes.

Cheers, Chris.
-- 
_ ___ __     _
  / __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer |
\ _/_/_/_//_/___/ | We are GNU-free your mind-and your software |

Subject: flowed test 2
From: Chris Wilson <[email-masked]>
To: [email-masked]
Date: Sun, 13 Feb 2005 18:03:01 +0000 (GMT)

     four spaces: flghk;lgkh; fgfg hl gf h;gk hl;fhk gf h;gkh ;fg
     gfljh;ko5rt p'ert;o troktg fo thkfotkh;k;lvghk ;f

 	one tab: d;fg krt;gk ptotpo t;fh ltrhjxijhweizfugurg g er idur dh
 	igh hgu hiudhguihrdghidxg

-- 
_ ___ __     _
  / __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer |
\ _/_/_/_//_/___/ | We are GNU-free your mind-and your software |

---

From: Matt Ackeret <[email-masked]>
Date: Sun, 13 Feb 2005 15:07:05 -0800 (PST)

>I think I have found a bug with Pine's flowed text feature, where it interacts
>badly with code-style indentations. The indents below will probably not appear
>if you run Pine 4.61 (as I do).

I'm on 4.62.  I have the quell-flowed-text feature on, and turned OFF the
prefer plain text part to see the flowed section below (the second part).
I manually copied the original text I saw into the viewer because not all
parts show up in the reply..  (If there's some setting I have that does this,
please someone inform me how to fix it -- basically I would like all
"text-like" parts to show up in a reply, in the editor.. not just the first
part.)

>     gfljh;ko5rt p'ert;o troktg fo thkfotkh;k;lvghk ;f

There're actually 5 spaces there.

>        idur dh igh hgu hiudhguihrdghidxg

There're 8 spaces there.

>        igh hgu hiudhguihrdghidxg

This was turned into 8 spaces.

>    [ Part 2: "flowed test 2 (fwd)" ]
>

That's four spaces properly.

>        igh hgu hiudhguihrdghidxg

Turned into 8 spaces.

There was also a third part, plain text, that looked like a plain version of
the above (note four spaces/one tab, not including the eight spaces part..)

---

From: Chris Wilson <[email-masked]>
Date: Sun, 13 Feb 2005 23:28:01 +0000 (GMT)

Hi Matt,

> "text-like" parts to show up in a reply, in the editor.. not just the first

Thanks for the response. I tried to enable quell-flowed-text with and 
without prefer-plain-text, and in neither case did I see the indents. That 
makes me think that this was fixed in 4.62. Can anyone confirm or deny or 
second this?

Cheers, Chris.

---

From: Matt Ackeret <[email-masked]>
Date: Sun, 13 Feb 2005 15:30:55 -0800 (PST)

On Sun, 13 Feb 2005, Chris Wilson wrote:
> Thanks for the response. I tried to enable quell-flowed-text with and without

Sorry, I forgot to say that quell-flowed-text only affects _creation_ of
flowed text, from my reading of the help text.. I wanted to mention it
just because it was a setting related to flowed text.

> prefer-plain-text, and in neither case did I see the indents. That makes me
> think that this was fixed in 4.62. Can anyone confirm or deny or second this?

Isn't it pretty easy to just upgrade and see?  or even if you only have a user
acct, compile it for yourself and try?

---

From: Chris Wilson <[email-masked]>
Date: Mon, 14 Feb 2005 00:07:54 +0000 (GMT)

Hi Matt,

> acct, compile it for yourself and try?

Sorry, I did that and it turns out that you're right, it is fixed in 4.62.
<grin type="sheepish" />

Thanks for your help, and sorry for the wasted bandwidth.

Cheers, Chris.

---

From: Eduardo Chappa <[email-masked]>
Date: Mon, 14 Feb 2005 11:00:20 -0800 (PST)

*** Matt Ackeret ([email-masked]) wrote on Feb 13, 2005:

> I'm on 4.62.  I have the quell-flowed-text feature on, and turned OFF 
> the prefer plain text part to see the flowed section below (the second 
> part). I manually copied the original text I saw into the viewer because 
> not all parts show up in the reply..  (If there's some setting I have 
> that does this, please someone inform me how to fix it -- basically I 
> would like all "text-like" parts to show up in a reply, in the editor.. 
> not just the first part.)

That's not possible. Pine includes only the first part in the composer 
when forwarding or replying to a message.

-- 
Eduardo
Patches/Help: http://www.math.washington.edu/~chappa/pine/
XML/RSS feed: http://www.math.washington.edu/~chappa/pine/pine.xml
Please send spam to webmaster@localhost

---

From: Matt Ackeret <[email-masked]>
Date: Mon, 14 Feb 2005 11:13:14 -0800 (PST)

On Mon, 14 Feb 2005, Eduardo Chappa wrote:
>> prefer plain text part to see the flowed section below (the second part). I
>> manually copied the original text I saw into the viewer because not all parts
>> show up in the reply..  (If there's some setting I have that does this,
> That's not possible. Pine includes only the first part in the composer when
> forwarding or replying to a message.

Then it's a bug, and could be fixed.

I realize pine does some things differently from other mail programs
(and I like that in many ways), but when I have to manually go out of my 
way to copy/paste (and correct quoting level) from the viewer to 
the composer, it shows a brokenness.

The time this shows most often is when there's text, an embedded picture,
and more text.  It's a pain in the neck to try to reply to some of the
later text.