From: Ken Raeburn <raeburn@cygnus.com>
Cc: ding@ifi.uio.no
Subject: Re: performance of fuzzy subject handling and killing threads
Date: 24 May 1996 16:58:58 -0400 [thread overview]
Message-ID: <tx1ras9kctp.fsf@cygnus.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 24 May 1996 17:41:51 +0200
Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
> Yes, I never use `k' myself. (Well, I just use `M-C-l' to kill
> articles; what with the threading and gathering, it kills exactly the
> same articles that `k' does in a fraction of the time.)
Sounds good, but it's dependent on how gathering and score handling
are configured. I'm not using scores at all, nor particularly
aggressive gathering. For me, M-C-l put a "-" on the summary lines
for the thread, and moved me to the next article of that thread.
next prev parent reply other threads:[~1996-05-24 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-24 10:24 Ken Raeburn
1996-05-24 15:41 ` Lars Magne Ingebrigtsen
1996-05-24 18:17 ` Jack Vinson
1996-05-24 18:44 ` Lars Magne Ingebrigtsen
1996-05-24 20:58 ` Ken Raeburn [this message]
1996-05-24 21:21 ` Lars Magne Ingebrigtsen
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=tx1ras9kctp.fsf@cygnus.com \
--to=raeburn@cygnus.com \
--cc=ding@ifi.uio.no \
/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).