Get Pico to "justify" the way Pine does?
alv...@xx.com
Pine justifies a paragraph with the > in front and keeps them at the
beginning of the each line. Shuffling everything to fit my 68 line
length setting. Works gereat. :)
The version of Pico I'm using is UW PICO 4.10 and doesn't do that,
I have to do it manually.
Is it Pico or am I needing to re/configure my setup differently or
what? :)
Another guy with a Panix shell account.
I've used Tin & Pico for newsgroups for about 12 years.
And in the last 5(?)years Pico for my website's HTML files.
Alvin in AZ
Eduardo Chappa
:) Pine justifies a paragraph with the > in front and keeps them at the
:) beginning of the each line. Shuffling everything to fit my 68 line
:) length setting. Works gereat. :)
:)
:) The version of Pico I'm using is UW PICO 4.10 and doesn't do that, I
:) have to do it manually.
Only recent versions of Pico (do not recall which one) support
justification of text that contain quote string, you would have to start
Pico with the command
pico -Q "> " file
in order to use such feature. Ask your provider to update the version of
Pico that they have installed.
--
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
alv...@xx.com
> :) my 68 line length setting. Works gereat. :) > :)
> :)
> :) The version of Pico I'm using is UW PICO 4.10 and doesn't do
> Only recent versions of Pico (do not recall which one) support
> justification of text that contain quote string, you would have
> to start Pico with the command
> pico -Q "> " file
> in order to use such feature. Ask your provider to update the
> version of Pico that they have installed.
> Eduardo
> Patches/Help: http://www.math.washington.edu/~chappa/pine/
> XML/RSS feed: http://www.math.washington.edu/~chappa/pine/pine.xml
Cool thanks. :)
Alvin in AZ
alv...@xx.com
> > Eduardo
Ooops. :)
Spent some time studying what you told me and realized I didn't make
my first post clear. :/ I'm extra good at that dumb trick. :/
When I get a large-quoted-paragraph in an email, using Pine, I can
hit ^J and the paragraph will be justified to my-set-68-line-length
and... all the >'s will line up on the left side automatically.
When I justify a paragraph with Pico the >'s will "slide along" with
the text and end up mixed all through the quoted texted. In a big
mess, not all lined up on the left end of each line, the way Pine
will do it.
That happens with -one- isolated long-line paragraph, ok?
Is there a difference of "paragraph justifying" capability between
Pine and Pico? (besides the need for isolating the paragraphs)
I realize the way Pine does it, is much more sophisticated. :)
And so wondering if Pico is even able to do that.
I'm a newsgroup junky and have been using Tin+Pico for about 12
years, it'd be really cool to get Pico to act like Pine in this
one way.
And you know as well as I do, a long thread will generate long line
lengths from all the added >'s, so the use/need is daily in my case.
BTW, Eduardo, your smiley face quote mark, is the first I've seen,
but have thought about doing something funny like that before. :)
Also thought about removing the space after my added >'s, too bad
that didn't start out as the default IMO.
Alvin in AZ
Chris Game
> When I justify a paragraph with Pico the >'s will "slide along" with
> the text and end up mixed all through the quoted texted. In a big
> mess, not all lined up on the left end of each line, the way Pine
> will do it.
That works ok in Nano - why not try that?
--
Chris Game
Gotta run, the cat's caught in the printer.
Eduardo Chappa
:) > > pico -Q "> " file
:) > > Eduardo
:)
:) When I get a large-quoted-paragraph in an email, using Pine, I can hit
:) ^J and the paragraph will be justified to my-set-68-line-length and...
:) all the >'s will line up on the left side automatically.
:)
:) When I justify a paragraph with Pico the >'s will "slide along" with
:) the text and end up mixed all through the quoted texted. In a big
:) mess, not all lined up on the left end of each line, the way Pine will
:) do it.
:)
:) That happens with -one- isolated long-line paragraph, ok?
:)
:) Is there a difference of "paragraph justifying" capability between Pine
:) and Pico? (besides the need for isolating the paragraphs)
I understood perfectly what you meant in your original post. I'll give you
a little bit of technical information about the way justification works,
so you understand everything.
Pico has always had justification, same as Pine/Alpine. They both use the
same algorithm for justification. The difference is if the quote string is
considered or not.
Pine sends to Pico the value of the quote string that the user uses, so it
knows how find it. Pico can not recognize a priori a quote string. It must
be told what the quote string is.
Because of this, when you use Pico as an external tool (you should use
"pico -t" as your editor), you must tell Pico somehow that you are going
to justify quoted text, and the quote string will be "> ". Otherwise, Pico
will not know that there is quoted text.
If you tell Pico that your quote string is "> ", it will find nested
levels (this is only available since Pine version 4.4X, at least 5 years
ago), but it will not realize about the quoted text below.
alvin> I realize the way Pine does it, is much more sophisticated. :)
alvin> And so wondering if Pico is even able to do that.
And the answer is yes, but as I said before Pico needs to be told what the
quote string is. In any case the algorithm in Pine (or Pico if told the
quote string) is good enough that it works for 99.9% of internet traffic.
Therefore use the command
pico -Q \"> \" file
and you will be on your way (or pico -Q \">\" file, depending on your
taste).
:) And you know as well as I do, a long thread will generate long line
:) lengths from all the added >'s, so the use/need is daily in my case.
And pico can handle those.
--
Eduardo
Patches/Help: http://www.math.washington.edu/~chappa/pine/
XML/RSS feed: http://www.math.washington.edu/~chappa/pine/pine.xml
Chris Game
>
> If you tell Pico that your quote string is "> ", it will find nested
> levels (this is only available since Pine version 4.4X, at least 5 years
> ago), but it will not realize about the quoted text below.
>
The quotation character is set by the poster of the message, not by
the reader. Some people use other characters like ":" .
--
Chris Game
"Just because I don't care doesn't mean I don't understand."
-- Homer Simpson
Eduardo Chappa
:) On 2007-03-14, Eduardo Chappa <cha...@math.washington.edu> wrote:
:) >
:) > If you tell Pico that your quote string is "> ", it will find nested
:) > levels (this is only available since Pine version 4.4X, at least 5
:) > years ago), but it will not realize about the quoted text below.
:)
:) The quotation character is set by the poster of the message, not by the
:) reader. Some people use other characters like ":" .
Well, yes and not. When *you* reply to a message *you* set the quote
string. That's what pico can get. If there is any other quote string
pico might not see it. Most people use ">" or "> ", and those can be
handled very well by pico. It is when you try stuff like ":)" or "Chris>"
that pico will choke on.
For example, you can configure pico so that it will reflow the following
text:
chris> this is an example of text that pico can be configured to reflow correctly
but pico will not reflow the following text correctly if you configure it
to use the quote string "> "
> chris> > In this example, pico or pine will only see the quote string "> ", even though the full quote string is "> chris> > ".
There are shortcomings, but most times things work out of the box.
It is my belief that nano thinks that all of quote strings are nested 1
character long quote strings, is that correct? (so nano would not, out of
the box, reflow correctly the above text either.)
Chris Game
> It is my belief that nano thinks that all of quote strings are
> nested 1 character long quote strings, is that correct? (so nano
> would not, out of the box, reflow correctly the above text
> either.)
Well I've no idea how nano works, it re-flowed the text but only
because it thought the first "> " was the quote string (the "chris"
bit wasn't repeated on the flowed line).
--
Chris Game
What is a "free" gift ? Aren't all gifts free?