Subject: disable displaying flowed text?

From: Ryan Barrett <[email-masked]>
Date: Tue, 1 Jun 2004 12:00:01 -0700 (PDT)

hi all. i really like the flowed text support in pine 4.60, and i 
definitely prefer to send it, so my recipients can use it if they like.

however, i'd prefer not to use it to display mail that i'm reading. i 
often run pine in terminals significantly wider than 80 characters, and 
it's hard to read the long lines of text that result from displaying 
flowed text.

is there any way i can turn off *displaying* flowed text? if not, could i 
add it as a feature request? if necessary, i'm happy to write a 
patch...well, after i finish another pine patch i'm working on. :P

-Ryan

--
"Woooo!!!"  -Twinsen
-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Eduardo Chappa <[email-masked]>
Date: Tue, 1 Jun 2004 12:07:43 -0700 (PDT)

*** Ryan Barrett ([email-masked]) wrote in the pine-info list today:

:) however, i'd prefer not to use it to display mail that i'm reading. i 
:) often run pine in terminals significantly wider than 80 characters, and 
:) it's hard to read the long lines of text that result from displaying 
:) flowed text.

Ryan,

  You can always set viewer-margin-left  and viewer-margin-right to 
improve your reading of messages, or you can press "H" and see the same 
message with format=flowed off. Of course the last command depends on if 
you have enabled [X] enable-full-header-cmd.

  I hope this helps.

Eduardo
http://www.math.washington.edu/~chappa/pine/

---

From: daniel lance herrick <[email-masked]>
Date: Tue, 1 Jun 2004 15:12:33 -0400 (EDT)

> patch...well, after i finish another pine patch i'm working on. :P

Does

   composer-wrap-column     = 50

affect the width for flowing text in the viewer?
Would it satisfy you, Ryan, if it did?

dan

---

From: Eduardo Chappa <[email-masked]>
Date: Tue, 1 Jun 2004 12:21:15 -0700 (PDT)

*** daniel lance herrick ([email-masked]) wrote in the...:

:) On Tue, 1 Jun 2004, Ryan Barrett wrote:
:) 
:) > hi all. i really like the flowed text support in pine 4.60, and i 
:) > definitely prefer to send it, so my recipients can use it if they 
:) > like.
:) >
:) > however, i'd prefer not to use it to display mail that i'm reading. i 
:) > often run pine in terminals significantly wider than 80 characters, 
:) > and it's hard to read the long lines of text that result from 
:) > displaying flowed text.
:) >
:) > is there any way i can turn off *displaying* flowed text? if not, 
:) > could i add it as a feature request? if necessary, i'm happy to write 
:) > a patch...well, after i finish another pine patch i'm working on. :P
:) 
:) Does
:) 
:)    composer-wrap-column = 50
:) 
:) affect the width for flowing text in the viewer?

No it does not. This has to do with the width of the text as seen in the 
composer and is enforced when you write text as well as when you justify 
(here the editor is Pico, the embedded editor, not an alternate editor).
The width of display is controlled by the margins to the left and to the 
right, there is no total width of the text since in f=f there is no 
assumption on the screen width, and doing otherwise would defeat the 
purpose of this format.

Eduardo

---

From: Ryan Barrett <[email-masked]>
Date: Tue, 1 Jun 2004 14:22:03 -0700 (PDT)

On Tue, 1 Jun 2004, Eduardo Chappa wrote:

> message with format=flowed off.

these are close, but not quite it. viewing with headers on works 
perfectly, except that i have to page through screenloads of headers, 
which is no good. the margin options are helpful, but don't quite work, 
since i use pine in terminals of varying widths. :/

ideally, i'd like an option that turns format=flowed on or off. (btw, 
eduardo, what is this format=... syntax?)

alternatively, i'd be happy with a viewer-wrap-column option that 
affects the viewer the same way composer-wrap-column affects pico.

-Ryan

--
"Woooo!!!"  -Twinsen

---

From: Kenneth Crudup <[email-masked]>
Date: Wed, 2 Jun 2004 15:34:19 -0700 (PDT)

>    composer-wrap-column     = 50

I'd hope the option to make that read the current xterm width, if
available, would be in there, too.

	-Kenny

-- 
Kenneth R. Crudup  Sr. SW Engineer, Scott County Consulting, Los Angeles
H: 3630 S. Sepulveda Blvd. #138, L.A., CA 90034-6809      (888) 454-8181
W: 26601 Agoura Road, Calabasas, CA 91302-1959            (818) 444-3685

---

From: Matt Ackeret <[email-masked]>
Date: Wed, 2 Jun 2004 15:55:19 -0700 (PDT)

>available, would be in there, too.

I think you're talking about pico, but at least when viewing messages, 
this does work -- I can resize the (Terminal, which also adheres to xterm
protocol, AFAIK) window, and if the message doesn't have hard returns, I'll see
wider lines.

---

From: Matt Ackeret <[email-masked]>
Date: Wed, 2 Jun 2004 16:42:31 -0700 (PDT)

>protocol, AFAIK) window, and if the message doesn't have hard returns, I'll see

aaah, interesting.  I was about to gripe about this particular message
still showing up funky..  When viewing the message, "see" showed up 
on its own line.. (this is when I was viewing the message, pre-adding the quote
char in this reply).

I went into the config and my composer-wrap-column was set to 79.
I changed it to 80, but it made no difference.  (This is me misunderstanding
what the "composer" is, I think, according to a personal reply I got 
yesterday).

But it'd be great if I were able to do this.

Bug-or-at-least-strangeness this made me find:

I thought maybe I could set the composer-wrap-column to 81 to sort of work
around the problem (or at least see if it made the issue go away on this
particular message).  If I try to set the composer wrap column above 80,
it says (I was playing with ridiculously large numbers):

       [Composer-wrap-column of 81100 not supported (Max 80). Using "80"]

But it still leaves my bogus number in there.  I think that if you have typed
too-large/small of a number there, it should clamp the number to the highest
(or lowest) valid number, and change the number I actually see there --- or
at the very least, change it when I save changes to the config screen..
i.e. if I go back in, it'll _then_ show me 80.