From: Cyrille Lefevre <clefevre@citeweb.net>
Cc: ding@gnus.org
Subject: Re: Gnus-5.8.7 new groups status "*", can't enter; "Incoming*" files
Date: Tue, 01 Aug 2000 01:17:53 +0200 [thread overview]
Message-ID: <aeexevoe.fsf@gits.dyndns.org> (raw)
In-Reply-To: Chris Shenton's message of "Mon, 31 Jul 2000 09:19:13 -0400"
Chris Shenton <cshenton@uucom.com> writes:
> Two problems I've noticed with 5.8.7 since a CVS pull of the
> pre-release, or maybe with 5.8.6. Seen on both FreeBSD and Solaris.
>
> 1. New nnml groups are displayed with status "*" and I can't enter
> them.
>
> I use procmail to file incoming mail into groups, then gnus picks
> them up. It (usually) shows the new group and I create a new
> procmail recipe and get mail in a new file/folder. But with status
> "*" when I try to enter the group it says something to the effect
> of "no such group". A look at the gnus store, which I keep under
> ~/Mail/newgroupname/", show the mail files getting populated
> properly.
>
> I can get into the group eventually by `K'illing the group, then
> `j'umping to the group name that I type in (e.g., nnml:list.gnus)
> which causes it to show as status "K"illed. I can `U'nkill the
> group and finally enter. Ick.
>
> Is it a bug or do I need to set something to create the new groups
> as "S"ubscribed or something?
try just g after you have created your new folder, or C-u space or return,
don't remember. I work this way, too, but w/ nnfolder :)
> 2. Leaves tmp files like ~/Mail/Incoming#####xyz
I have these, too.
Cyrille.
--
home: mailto:clefevre@citeweb.net work: mailto:Cyrille.Lefevre@edf.fr
next prev parent reply other threads:[~2000-07-31 23:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-31 13:19 Chris Shenton
2000-07-31 22:53 ` Kevin Falcone
2000-07-31 23:17 ` Cyrille Lefevre [this message]
2000-07-31 23:36 ` Chris Shenton
2000-08-01 2:06 ` Cyrille Lefevre
2000-08-01 2:52 ` Chris Shenton
2000-08-01 3:15 ` Cyrille Lefevre
2000-08-01 7:37 ` Kai Großjohann
2000-08-01 12:23 ` David S. Goldberg
2000-08-01 13:33 ` David S. Goldberg
2000-08-01 17:43 ` Chris Shenton
2000-08-02 8:31 ` Kai Großjohann
2000-08-02 14:49 ` Paul Jarc
2000-08-02 19:24 ` Kai Großjohann
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=aeexevoe.fsf@gits.dyndns.org \
--to=clefevre@citeweb.net \
--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).