From: jzawodn@wcnet.org (Jeremy D. Zawodny)
Cc: ding@gnus.org
Subject: Re: Incoming* files
Date: 27 Oct 1998 19:19:00 -0500 [thread overview]
Message-ID: <m3yaq1r11n.fsf@poof.z.org> (raw)
In-Reply-To: Maciej Matysiak's message of "28 Oct 1998 02:06:35 +0100"
Maciej Matysiak <phoner@blah.pl> writes:
> phoner@ogryzek~/Mail/ ls Incoming* |wc -l
> 6920
>
> what are those files? it seems it's all my mail since i started
> using pgnus. can i simply delete them? all the incoming should be
> simply split into few groups (and it is in fact).
Using nnmail? Try putting this in your .gnus:
(setq nnmail-delete-incoming t)
Jeremy
--
Jeremy D. Zawodny Web Geek, Perl Hacker, etc.
http://www.wcnet.org/~jzawodn/ jzawodn@wcnet.org
LOAD "LINUX",8,1
next prev parent reply other threads:[~1998-10-28 0:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-28 1:06 Maciej Matysiak
1998-10-28 0:19 ` Jeremy D. Zawodny [this message]
1998-10-28 0:46 ` Maciej Matysiak
1998-10-28 0:58 ` Justin Sheehy
1998-10-28 1:05 ` Chris Tessone
1998-10-28 1:43 ` Maciej Matysiak
1998-10-28 1:44 ` Jeremy D. Zawodny
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=m3yaq1r11n.fsf@poof.z.org \
--to=jzawodn@wcnet.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).