From: Lee Willis <lee@gbdirect.co.uk>
Subject: Problem with pgnus (Various versions ...)
Date: 16 Jun 1999 14:10:43 +0100 [thread overview]
Message-ID: <lzogig2svg.fsf@landlord.gbdirect.co.uk> (raw)
I've got a problem with pgnus (Currently v0.88 but I don't think it's
version dependent, and may even be present in gnus)
I come into work and start pgnus, it reads all my new mail, filters it
beautifully, and shows me which groups have new mail. If I press L I see
all groups regardless of whether or not they have unread mail *except*
for one. This group doesn't show up at all until it receives more new
mail or until I 'touch' the file that pgnus reads from (In this case
~/mail/Fvwm-Dev). I can't see anything wrong with the active or
.newsrc.eld files but then again I wouldn't be too sure what exactly to
look for. I have seen this behaviour before with another group. I solved
it by deleting the group and recreating it (Losing all the mail in that
folder, I couldn't be bothered preserving it!).
Any ideas where I should start looking to find the problem?
The active entry looks like :
Fvwm-Dev 4156 3888 y
and the .newsrc.eld :
Hmm, whoops I appear to have the following files ...
.newsrc.eld
(setq gnus-newsrc-file-version "Pterodactyl Gnus v0.77")
(setq gnus-newsrc-last-checked-date '"Thu Feb 25 16:50:03 1999")
[Snipped rest]
.newsrc-news
[Empty]
.newsrc-news.eld
(setq gnus-newsrc-file-version "Pterodactyl Gnus v0.88")
(setq gnus-newsrc-options '"")
(setq gnus-newsrc-last-checked-date '"Wed Jun 16 11:23:53 1999")
[Snipped rest]
Could this be the problem. Anyways since the latter seems to be the one
being used here is the bit about Fvwm-Dev
("nnfolder+private:Fvwm-Dev" 3 ((1 . 4161)) ((reply 3984))
"nnfolder:private" ((total-expire . t)))
Any ideas?
Lee.
--
I was doing object-oriented assembly at 1 year old ...
For some reason my mom insists on calling it "Playing with blocks"
next reply other threads:[~1999-06-16 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-16 13:10 Lee Willis [this message]
1999-07-03 9:48 ` 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=lzogig2svg.fsf@landlord.gbdirect.co.uk \
--to=lee@gbdirect.co.uk \
/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).