From: "Georg C. F. Greve" <greve@fsfeurope.org>
To: ding@gnus.org
Subject: Re: Getting rid of the zombies in dynamically created groups
Date: Thu, 27 Sep 2007 23:35:39 +0200 [thread overview]
Message-ID: <m38x6rsses.fsf@cerebro.fsfeurope.org> (raw)
In-Reply-To: <v9k5qcocvr.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Thu, 27 Sep 2007 08:12:24 +0200")
[-- Attachment #1: Type: text/plain, Size: 1669 bytes --]
On Thu, 27 Sep 2007 08:12:24 +0200
Reiner Steib <reinersteib+gmane@imap.cc> wrote:
>> How hard would it be to give gnus the capability to ignore what it
>> thinks to know about a group and force it to reread as if it were a
>> new group? I lack the knowledge to do so myself, but it doesn't
>> sound like a terribly impossible thing to do...
rs> Maybe `gnus-group-clear-data', cf. (info "(gnus)Group Data")?
Trying this apparently screwed up nnmaildir entirely. :-/
When I try to enter the group, I see
Retrieving newsgroup: nnmaildir:mairix...
Fetching headers for nnmaildir:mairix...done
Suppressing duplicates...done
No articles in the group
No more unread newsgroups
No unread news
which is a lie, when doing ls -lR in the folder, I see
greve@cerebro:~/.nnmaildir/mairix$ ls -lR
.:
total 12
drwx------ 2 greve greve 4096 2007-09-27 23:30 cur
drwx------ 2 greve greve 4096 2007-09-27 23:30 new
drwx------ 2 greve greve 4096 2007-09-27 22:55 tmp
./cur:
total 104
-rw-r--r-- 1 greve greve 100919 2007-09-27 23:30 123456789.89799.mairix:2,
./new:
total 0
./tmp:
total 0
so there is an article in the group, but there seems to be no way to
enter it, or to get Gnus to see that article. Tried deleting and
readding the group, but that also didn't help.
Help appreciated.
Regards,
Georg
--
Georg C. F. Greve <greve@fsfeurope.org>
Free Software Foundation Europe (http://fsfeurope.org)
Join the Fellowship and protect your freedom! (http://www.fsfe.org)
What everyone should know about DRM (http://DRM.info)
[-- Attachment #2: Type: application/pgp-signature, Size: 306 bytes --]
next prev parent reply other threads:[~2007-09-27 21:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 13:52 Georg C. F. Greve
2007-09-26 18:38 ` Reiner Steib
2007-09-26 22:38 ` Georg C. F. Greve
2007-09-27 6:12 ` Reiner Steib
2007-09-27 21:35 ` Georg C. F. Greve [this message]
2007-10-04 8:04 ` released mairix backend nnmairix.el (was: Getting rid of the zombies in dynamically created groups) David
2007-10-04 16:29 ` released mairix backend nnmairix.el Reiner Steib
2007-10-05 9:15 ` David
2007-10-05 16:41 ` Reiner Steib
2007-10-06 14:24 ` Georg C. F. Greve
2007-10-06 18:59 ` Bastien
2007-10-06 21:20 ` David
2007-10-06 23:19 ` Bastien
2007-10-07 16:09 ` David
2007-10-08 9:33 ` Bastien
2007-10-06 21:17 ` David
2007-10-06 23:17 ` Bastien
2007-10-07 11:12 ` Georg C. F. Greve
2007-10-07 15:53 ` David
2007-10-08 9:33 ` Bastien
2007-10-04 16:48 ` released mairix backend nnmairix.el (was: Getting rid of the zombies in dynamically created groups) Bastien
2007-10-04 17:18 ` released mairix backend nnmairix.el Bastien
2007-10-05 9:46 ` David
2007-10-05 12:00 ` Bastien
2007-10-04 23:54 ` Bastien
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=m38x6rsses.fsf@cerebro.fsfeurope.org \
--to=greve@fsfeurope.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).