From: gsstark@MIT.EDU (Greg Stark)
Subject: scoring bugs, problems, and suggestions
Date: 19 Mar 1996 20:21:36 -0500 [thread overview]
Message-ID: <ycq7mwgmue7.fsf@fierce-bad-rabbit.MIT.EDU> (raw)
September Gnus v0.51; nntp 4.0; nnml 1.0; nnmh 1.0; nneething 1.0; nndoc 1.0; nndraft 1.0; nnfolder 1.0
GNU Emacs 19.30.1 (mips-dec-ultrix4.2, X toolkit) of Mon Jan 8 1996 on yaz-pistachio
I recently added a `head' score rule for my mail to mark duplicated messages
as read and Gnus started messaging for each article it scored. Based on my
experience with this a series of suggestions have come to mind, some of these
i consider bugs, some will unfortunately have to wait for Red Gnus:
1) put the Gnus-Warning header in mail overview files
in fact, allow me to put whatever headers i want in my overview files
2) allow me to save the scores of some groups but not others
since i only tend to read articles more than once in mail groups.
a token in the score file sounds better than a regexp imho.
3) sort numbers in numeric, not alphabetic order, duh.
4) I would actually expect number of articles scored and
total number of articles needing scoring would be more
useful than actual article numbers because of gaps and threads.
5) get a much better guess of how many articles need to be scored
you have a lot more information at this stage than in the Group buffer
and you seem to be counting only new articles regardless of the
number of articles being displayed and regardless of gnus-save-score
*Messages* buffer:
================================================================
> Scoring...
> Scoring on article 1 of 1...
> Scoring on article 10 of 1...
> Scoring on article 11 of 1...
> Scoring on article 12 of 1...
> Scoring on article 13 of 1...
> Scoring on article 14 of 1...
> Scoring on article 15 of 1...
> Scoring on article 16 of 1...
> Scoring on article 17 of 1...
> Scoring on article 18 of 1...
> Scoring on article 19 of 1...
> Scoring on article 2 of 1...
> Scoring on article 20 of 1...
> Scoring on article 21 of 1...
> Scoring on article 22 of 1...
> Scoring on article 23 of 1...
> Scoring on article 24 of 1...
> Scoring on article 25 of 1...
> Scoring on article 26 of 1...
> Scoring on article 27 of 1...
> Scoring on article 28 of 1...
> Scoring on article 29 of 1...
> Scoring on article 3 of 1...
> Scoring on article 30 of 1...
> Scoring on article 31 of 1...
> Scoring on article 32 of 1...
> Scoring on article 33 of 1...
> Scoring on article 34 of 1...
> Scoring on article 4 of 1...
> Scoring on article 5 of 1...
> Scoring on article 6 of 1...
> Scoring on article 7 of 1...
> Scoring on article 8 of 1...
> Scoring on article 9 of 1...
> Scoring...done
================================================================
next reply other threads:[~1996-03-20 1:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-03-20 1:21 Greg Stark [this message]
1996-03-20 19:19 ` Lars Magne Ingebrigtsen
1996-03-20 23:18 ` Greg Stark
1996-03-21 18:12 ` 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=ycq7mwgmue7.fsf@fierce-bad-rabbit.MIT.EDU \
--to=gsstark@mit.edu \
/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).