Killing a thread?
Niklaus Kuehnis
In the Pine 4.64 newsreader for Linux, is it possible to kill a
thread so that not only all present messages are excluded but also
all future followups won't appear? I would need this to read groups
with long threads and high traffic.
Second, is it possible to open newsgroups with threads collapsed?
Thanks.
--
Nik
Eduardo Chappa
:) In the Pine 4.64 newsreader for Linux, is it possible to kill a thread
:) so that not only all present messages are excluded but also all future
:) followups won't appear? I would need this to read groups with long
:) threads and high traffic.
No, you can only delete current messages in a thread. Having said that,
you can create a filter (M S R F) that deletes messages with a given
subject, but not as being in a given thread. I believe that this would
make Pine much more slower, so give it a try and see what happens.
:) Second, is it possible to open newsgroups with threads collapsed?
There is a global configuration option called threading-index-style, which
you would like to set as below.
threading-index-style =
Set Rule Values
--- ----------------------
( ) regular-index-with-expanded-threads
( ) regular-index-with-collapsed-threads
( ) separate-index-screen-always
(*) separate-index-screen-except-for-single-messages
The main problem that you would have is that this would apply to all
folders (e-mail and news).
I have a patch, that among other things, allows you to set this option on
a per-folder basis. The patch is called "define your own rules..." and can
be obtained in my web page. An example of how to configure Pine with the
patch is given below:
threading-index-style-rule = _FOLDER_ == {comp.mail.pine} => _THREADINDEX_{separate-index-screen-except-for-single-messages}
_COLLECTION_ >> {Incoming-Folders;News} => _THREADINDEX_{separate-index-screen-except-for-single-messages}
I hope this helps you
--
Eduardo
Patches/Help: http://staff.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
Free speech means you have to be subjected to crap sometimes. :/
Just the way it is. :)
Alvin in AZ
Niklaus Kuehnis
> *** Niklaus Kuehnis (bakuehn...@gmx-topmail.de.comm) wrote in...:
>
> :) In the Pine 4.64 newsreader for Linux, is it possible to kill a thread
> :) so that not only all present messages are excluded but also all future
> :) followups won't appear? I would need this to read groups with long
> :) threads and high traffic.
>
> No, you can only delete current messages in a thread. Having said that,
> you can create a filter (M S R F)
That's rather complicated. I'm presently comparing pine's newsreader
to tin. In tin I can create a filter on the subject (AFAIK) with a
single shortcut ("]"). tin's one step ahead, there, I guess. ;-)
[snip]
> :) Second, is it possible to open newsgroups with threads collapsed?
>
[snip]
> threading-index-style =
> Set Rule Values
> --- ----------------------
> ( ) regular-index-with-expanded-threads
> ( ) regular-index-with-collapsed-threads
> ( ) separate-index-screen-always
> (*) separate-index-screen-except-for-single-messages
>
> The main problem that you would have is that this would apply to all
> folders (e-mail and news).
I chose regular-index-with-collapsed... for a try and I haven't found
any collapsed threads in my e-mail inbox, but the newsgroups open
with threads collapsed and look a lot better. That's a step forward
already.
> [own rules patch]
No need for that one at the moment. Thanks anyway.
> I hope this helps you
It does indeed, thanks!
--
Nik
Niklaus Kuehnis
> Besides what Ed said, kill files are for sissies. ;)
I don't like filtering by sender but I would consider a function like
"killing the rest of the thread" to be a useful function in a
newsreader. It's more like "mark read" than killfiling. ;-)
> Free speech means you have to be subjected to crap sometimes. :/
Of course, unsubscribing often helps. :)
--
Nik
Helmut Richter
> Free speech means you have to be subjected to crap sometimes. :/
Free speech does not oblige the hearers to listen.
--
Helmut Richter
Harold Stevens
[Snip...]
> Free speech does not oblige the hearers to listen.
Precisely. Without filters, net speech to me is a nearly useless loony bin.
JMO; YMMV...
--
Regards, Weird (Harold Stevens) * IMPORTANT EMAIL INFO FOLLOWS *
Pardon any bogus email addresses (wookie) in place for spambots.
Really, it's (wyrd) at airmail, dotted with net. DO NOT SPAM IT.
Kids jumping ship? Looking to hire an old-school type? Email me.
alv...@xx.com
> I don't like filtering by sender but I would consider a function
> like "killing the rest of the thread" to be a useful function in
> a newsreader. It's more like "mark read" than killfiling. ;-)
> > Free speech means you have to be subjected to crap sometimes. :/
> Of course, unsubscribing often helps. :)
Ahhh... I see now. ;)
(i'm kinda slow)
Ok cool, you ain't "running away" ...that's good to hear. :)
Doggonit I don't know the answer other than to use Tin and < c > for
"catch-up" that makes Tin think you already-done-read the newsgroup
or thread or post... depending on where in the tree stucture you're
at. :)
Did that help at all? :/
Tin with Pico as the word-wrangler is pretty slick for Pine-heads! :)
YMMV
I use several "alias" and two of them are
"pine = pine -d0"
"tinx = tin -Q"
You can't "yank-in" < y > all the newsgroups with "tin -Q" so gotta
save "tin" just for that use.
Still haven't figured out how to get "pico -d" to work inside Tin
tho. :/
Alvin in AZ
Niklaus Kuehnis
> Doggonit I don't know the answer other than to use Tin and < c > for
> "catch-up" that makes Tin think you already-done-read the newsgroup
> or thread or post... depending on where in the tree stucture you're
> at. :)
>
> Did that help at all? :/
Yes, thanks. And to ignore the rest of the thread - including the
future messages - I need to use < ] >. Or is there any simpler way to
do that?
> Tin with Pico as the word-wrangler is pretty slick for Pine-heads! :)
Nice to hear I'm on the right path. :)
> [pine and tin aliases and options]
Thanks. Already sorted that out.
> Still haven't figured out how to get "pico -d" to work inside Tin
> tho. :/
I suppose you have set EDITOR to "pico -d"?
--
Nik
alv...@xx.com
> > ...use Tin and < c > for "catch-up" that makes Tin think you
> > on where in the tree stucture you're at. :)
> future messages - I need to use < ] >. Or is there any simpler way
> to do that?
You are now ahead of me on this. :)
I'm still back at the "C" level of doing things. :)
Not too often I need to use it on whole threads anyway.
> > Still haven't figured out how to get "pico -d" to work inside
> > Tin tho. :/
> I suppose you have set EDITOR to "pico -d"?
> Nik
I tried, but it breaks my "TinRC" since I'm not doing it right. :/
My TinRC has...
default_editor_format=%E +%W -68 %F
I don't understand what to do. :/
I changed the line length to 68 but whenever I try anything else
like add "pico -d" it defaults to vi which I don't know how to use.
Anybody got any ideas? :)
I tried getting some sort of tutorial on this small aspect of
"RC file programming" and couldn't find "little" stuff like that.
All the help seems to be geared toward big problems. :)
Somebody help me with this and I'll help others with it, that's how
I do stuff. :)
Alvin in AZ
Stephen Chadfield
> I suppose you have set EDITOR to "pico -d"?
In my ~/.tin/tinrc I have:
default_editor_format=pico -s wrap-aspell -r72 -t +%N %F
The spell checker is just a little wrapper:
#!/bin/bash
aspell -e -c $*
I have tried using Pine for news but it is just too clumsy.
--
Stephen Chadfield
Niklaus Kuehnis
[snip]
>> I suppose you have set EDITOR to "pico -d"?
>> Nik
>
> I tried, but it breaks my "TinRC" since I'm not doing it right. :/
>
> My TinRC has...
> default_editor_format=%E +%W -68 %F
>
> I don't understand what to do. :/
> I changed the line length to 68 but whenever I try anything else
> like add "pico -d" it defaults to vi which I don't know how to use.
I'm still not sure: Did you set the $EDITOR variable in bash? Like:
export EDITOR="pico -d"
I think the %E in tinrc is replaced by $EDITOR.
[snip]
--
Nik
alv...@xx.com
> I'm still not sure: Did you set the $EDITOR variable in bash?
Yes I did, now that you guys helped me. :)
Thanks a bunch on that! :)
I used Stephen Chadfield's example tho.
Just simply replaced the %E with... pico -d
Used Pico to do that of course. ;)
Carefully going over the "man pico" I tried "pico -w" and a couple
other things but nothing makes Pico act like Pine when justifying
a paragraph.
Pine keeps all the >'s to the left and moves the words around and
Pico moves the >'s along with the justified words and mixes the >'s
all through the paragraph.
Maybe Pico can't do what Pine can do, when justifying a paragraph?
I'm using Pico 4.10... what Panix has got set up.
"pico -d" changes the backspace key, not good. ;)
12 years of using Pico without the -d option... this is no time to
switch that now. ;)
Whether I get Pico to do what I want or not, I really appreciate
the help with the tinrc file. :) I understand it now.
Alvin in AZ
Eduardo Chappa
:) Carefully going over the "man pico" I tried "pico -w" and a couple
:) other things but nothing makes Pico act like Pine when justifying a
:) paragraph.
This appears in "man pico"
-Q quotestr
Set the quote string. Especially useful when composing
email, setting this allows the quote string to be checked
for when Justifying paragraphs. A common quote string is
"> ".
:) Maybe Pico can't do what Pine can do, when justifying a paragraph? I'm
:) using Pico 4.10... what Panix has got set up.
the -Q option was added to the version of Pico released with Pine 4.51,
while Pico 4.10 was released together with Pine 4.63, so your Pico should
have the option -Q.
Try using, from the command line, "pico -h". A list of options should
appear there, can you see the "-Q" option?
--
Eduardo
Patches/Help: http://www.math.washington.edu/~chappa/pine/
alv...@xx.com
> This appears in "man pico"
> -Q quotestr
> Set the quote string. Especially useful when composing email,
> setting this allows the quote string to be checked for when
> Justifying paragraphs. A common quote string is "> ".
Your paragraph "as is"...
> the -Q option was added to the version of Pico released with Pine 4.51,
> while Pico 4.10 was released together with Pine 4.63, so your Pico should
> have the option -Q.
-------
Your paragraph justfied to line length 68 using Pine...
> the -Q option was added to the version of Pico released with Pine
> 4.51, while Pico 4.10 was released together with Pine 4.63, so
> your Pico should have the option -Q.
-------
Your paragraph justfied to line length 68 using Pico...
> the -Q option was added to the version of Pico released with Pine
4.51, > while Pico 4.10 was released together with Pine 4.63, so
your Pico should > have the option -Q.
------
Pine kicks butt when it justifies a paragraph. :)
> Try using, from the command line, "pico -h". A list of options
> should appear there, can you see the "-Q" option?
> Eduardo
Yes, I tried -Q and -Q0. :)
Isn't that the option you used to get the ":) " instead of "> "?
Alvin in AZ
Eduardo Chappa
>> Try using, from the command line, "pico -h". A list of
>> options should
>> appear there, can you see the "-Q" option? Eduardo
>
> Yes, I tried -Q and -Q0. :)
>
> Isn't that the option you used to
> get the ":) " instead of "> "?
Try, from the command line, using the command
pico -Q "> "
and cut and paste this message to that session of pico, then press ^J in
the quoted text above and you will see pico justifying text and
considering during justification the ">".
having said all this, pico will not add the quote string for you. When you
reply to a message, Pine will put that quote string for you according to
the value of the option reply-indent-string, that's how i get my ":) ".
alv...@xx.com
> pico -Q "> "
Yeeeee Haaaaw! :)
It works! :)
Thanks Eduardo. :)
If you only knew how much work that's going to save me. :)
Alvin in AZ