Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Falcone <kevinfal@seas.upenn.edu>
Subject: Re: Gnus-5.8.7 new groups status "*", can't enter; "Incoming*" files
Date: Mon, 31 Jul 2000 18:53:04 -0400	[thread overview]
Message-ID: <m3bszddi9b.fsf@bowline.jibsheet.com> (raw)
In-Reply-To: Chris Shenton's message of "Mon, 31 Jul 2000 09:19:13 -0400"

>>>>> "CS" == Chris Shenton <cshenton@uucom.com> writes:

  CS>    I can get into the group eventually by `K'illing the group,
  CS>    then `j'umping to the group name that I type in (e.g.,
  CS>    nnml:list.gnus) which causes it to show as status "K"illed. I
  CS>    can `U'nkill the group and finally enter.  Ick.

What happens if you run M-g on the group? I usually have to do that on
new groups the first time.  

You might also want to look at gnus-subscribe-newsgroup-method
        
  CS>    Gnus since 5.8.6 or 5.8.7 CVS and now Release have been
  CS>    leaving what appears to be temporary files in the mail store
  CS>    area, which I have as ~/Mail/.

Yes, this is to back up your mail in case Gnus decides to have an
early lunch.  You can stop this with

(setq mail-source-delete-incoming t)

-kevin

-- 
Lasciate ogni speranza, voi ch'entrate!
			--Dante



  reply	other threads:[~2000-07-31 22:53 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 [this message]
2000-07-31 23:17 ` Cyrille Lefevre
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=m3bszddi9b.fsf@bowline.jibsheet.com \
    --to=kevinfal@seas.upenn.edu \
    /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).