From: Dirk Meyer <dmeyer@tzi.de>
Subject: killing subthread
Date: Thu, 09 Aug 2001 16:47:08 +0200 [thread overview]
Message-ID: <xt4snf1z3wz.fsf@riemen.informatik.uni-bremen.de> (raw)
Hi,
I have a problem killing subthreads. E.g. I have a thread like this:
[ article ]
[ article 1 ]
[ article 1.1 ]
[ article 2 ]
[ article 2.1 ]
When I read the top article and reenter the group, the thread looks
like this:
[ article 1 ]
[ article 1.1 ]
< article 2 >
[ article 2.1 ]
That's what I want: one thread containing all loose threads. Now I read
article 1 and think: "off topic", I don't want to read this
subthread. How can I kill the subthread 1 without killing subthread 2?
When I invoke gnus-summary-kill-thread all articles are killed.
I want to mark the article 1 as killed and all articles from this
subthread as killed (or read) and then I use adaptive scoring to make
sure I don't read anything from this subthread again. But I want all
articles from subthread 2 marked as unread.
Dirk
--
Time is a drug. Too much of it kills you.
-- in Small Gods (Terry Pratchett)
next reply other threads:[~2001-08-09 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 14:47 Dirk Meyer [this message]
2001-08-17 16:42 ` Lars Magne Ingebrigtsen
2001-08-17 17:20 ` Kai Großjohann
2001-08-17 18:01 ` Per Abrahamsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xt4snf1z3wz.fsf@riemen.informatik.uni-bremen.de \
--to=dmeyer@tzi.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).