From: jidanni@jidanni.org
To: ding@gnus.org
Subject: utterly bogus "How many articles from ... (available ..., default ...)"
Date: Mon, 13 Jun 2011 19:58:56 +0800 [thread overview]
Message-ID: <87pqmi54e7.fsf@jidanni.org> (raw)
You know, this line
How many articles from mail.debianbugs (available 388, default 200):
is misleading.
One sees it when about to enter a group in which all articles are
already read.
You see I often use
E runs the command gnus-summary-mark-as-expirable,
So in fact all that really are in that directory are
$ ls -vx
9 22 27 28 30 31 37 46 81 90 93 96 123 135 181 216 217 218 253 254
258 276 300 302 356 357 394 395 396
Which agrees with the overview file.
$ cut -f 1 .overview > /tmp/s
$ ls -v|diff - /tmp/s
$
Ha! 396 - 9 ~= 388. It just "never expected" there might be holes in the middle.
It just assumes there aren't. It doesn't know,
http://www.youtube.com/watch?v=lQ57rtIv7kk&p=6E40919035151385
Another big problem is OK, given there are
$ ls |wc -l
29
messages there, one might expect if I answer "29" when asked How many
articles, that's what I'll get.
However of course I only get 3. As there are only 3 articles actually
there within the 29 latest supposed existing articles.
If I really want to see all 29 articles, I had better type 396 when
asked, or the easier to type 444, 555, etc.
However the common person doesn't know that and his older articles now
become inaccessible to him, even though there are there on the disk.
So you gnus fellow have a lot of fixing to do.
I bet you are using a newsgroup mentality carried over to groups where
message removal is possible.
By the way, here is my .newsrc.eld section,
("nnml:mail.debianbugs" 3
((1 . 396))
((seen (1 . 396)) (save 96 395) (expire (394 . 396)) (reply 28 31 81 90 93 123 181 (253 . 254) 258 276 302 (356 . 357) (394 . 395))) "nnml:"
((timestamp 19957 62151)))
And the .marks file.
((expire 355 (358 . 396)) (reply 28 31 81 90 93 105 (114 . 118) (122 .
123) (131 . 132) 134 136 138 146 149 (153 . 154) 158 163 177 (181 . 186)
(188 . 189) 191 195 198 (202 . 204) (224 . 225) 230 232 (244 . 246) (253
. 254) 258 276 302 340 344 (347 . 348) (350 . 351) (355 . 362) 368 371
374 383 (385 . 388) 391 (394 . 395)) (save 96 103 118 150 (196 . 197)
362 395) (read (1 . 347)))
My configuration files are on http://jidanni.org/comp/configuration/
And rest assured I use very new gnus,
emacs-snapshot:
Installed: 1:20110608-1
next reply other threads:[~2011-06-13 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 11:58 jidanni [this message]
2011-06-26 9:43 ` Lars Magne Ingebrigtsen
2011-06-26 10:17 ` Peter Münster
2011-06-26 10:21 ` Lars Magne Ingebrigtsen
2011-06-28 1:09 ` jidanni
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=87pqmi54e7.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--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).