From: Steinar Bang <sb@metis.no>
Subject: Re: 5.6.9: nnml group beeps on entry
Date: 02 Jun 1998 13:53:34 +0200 [thread overview]
Message-ID: <whaf7wxbnl.fsf@viffer.oslo.metis.no> (raw)
In-Reply-To: Hrvoje Niksic's message of "02 Jun 1998 12:24:24 +0200"
>>>>> Hrvoje Niksic <hniksic@srce.hr>:
> Steinar Bang <sb@metis.no> writes:
>> > Have a peek in the *Messages* buffer if you hear a beep.
> [...]
>> I now read mail and news in XEmacs 20.4 which I had to start using
>> to get tm to work again (the alternative would have been to
>> downgrade to 19.34), and XEmacs doesn't seem to have a *Messages*
>> buffer.
> Press `C-h l' instead. Much better than *Messages*.
Ah-mazing! This one had
...
Recent minibuffer messages (most recent first):
Generating summary...done
Generating summary...
Sorting threads...done
Sorting threads...
Fetching headers for nnml:mail.dod...done
Strange nov line (461)
Fetching headers for nnml:mail.dod...
Retrieving newsgroup: nnml:mail.dod...
Loading view-less...done
Loading view-less...
...
And ~/Mail/mail/dod/.overview:461 looked like this:
3798ne.oslo.metis.no mail.dod:3714
Removing that line got rid of the beep. Regenerating all NOV files
using
M-x gnus-cache-generate-nov-databases RET
didn't fix it, and didn't seem to do anything except to lose me my
cached articles in newsgroups. The cached articles are still in the
.newsrc.eld files, as far as I can tell,
("comp.risks" 3 ((1 . 764)) ((cache 180 (184 . 186) 190 (194 . 195) 197 (200 . 202) 207 (209 . 210) 212 216 (223 . 227) 229 (231 . 236) (238 . 240) 245) (tick 736 (763 . 764))))
But they don't show up when I enter the newsgroup.
prev parent reply other threads:[~1998-06-02 11:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-28 10:42 Steinar Bang
1998-05-28 12:44 ` Lars Balker Rasmussen
1998-05-28 14:14 ` Steinar Bang
1998-05-29 9:11 ` Steinar Bang
1998-06-01 3:39 ` Lars Magne Ingebrigtsen
1998-06-02 10:05 ` Steinar Bang
1998-06-02 10:24 ` Hrvoje Niksic
1998-06-02 11:53 ` Steinar Bang [this message]
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=whaf7wxbnl.fsf@viffer.oslo.metis.no \
--to=sb@metis.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).