Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Kill all messages in buffer
Date: Sat, 27 Sep 2014 09:30:17 -0400	[thread overview]
Message-ID: <m2iok9mbrq.fsf@lifelogs.com> (raw)
In-Reply-To: <87k34p7ec8.fsf@pedroche.home>

On Sat, 27 Sep 2014 08:43:51 +0200 Igor Sosa Mayor <joseleopoldo1792@gmail.com> wrote: 

ISM> Ted Zlatanov <tzz@lifelogs.com> writes:
>> Oh, that's totally different.  You want to lower these threads' scores
>> en masse.

ISM> exactly! Maybe I should think of programming some small function... Or
ISM> is there already a solution for this?

I don't think this has been requested before.

Start with (info "(gnus) Scoring")

First of all, note that Gnus does have kill files but they are slow and
probably not what you're looking for.

You can use scoring to lower any thread's score.

Look at `gnus-summary-increase-score` for the UI around it, which
constructs a call to `gnus-summary-score-entry`.  It only does a single
score right now, so you'd either have to write some ELisp or construct a
keyboard macro (far easier but less maintainable).  I'd recommend the
macro to see if you want to use this at all.  The effort of using the
macro is *probably* the same as the effort of marking each thread and
calling a function.

My concern there is that the message IDs for killed threads will pile up
and the scoring code is not optimized for lookups. You may end up with a
really long time waiting for the summary buffer. To combat that, you can
use individual score files per group and decaying scores.

HTH
Ted




  reply	other threads:[~2014-09-27 13:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-24 14:24 Igor Sosa Mayor
2014-09-26 11:32 ` Christoph Groth
2014-09-26 15:25   ` Igor Sosa Mayor
2014-09-26 22:46     ` Ted Zlatanov
2014-09-27  6:43       ` Igor Sosa Mayor
2014-09-27 13:30         ` Ted Zlatanov [this message]
2014-09-27 14:05           ` Igor Sosa Mayor
2014-09-29  9:24     ` Christoph Groth
2014-09-30 10:32       ` Igor Sosa Mayor

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=m2iok9mbrq.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    /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).