Gnus development mailing list
 help / color / mirror / Atom feed
From: "Adam Sjøgren" <asjo@koldfront.dk>
To: ding@gnus.org
Subject: Re: Moving the Incoming* safety files to a separate directory
Date: Wed, 26 Feb 2020 21:50:39 +0100	[thread overview]
Message-ID: <87v9ntxecg.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87tv3d5bqt.fsf@mid.deneb.enyo.de>

Florian writes:

> Is there a way to tell Gnus to keep those files in a separate
> directory?

I think this is the variable to change:

,----[ C-h v mail-source-directory RET ]
| mail-source-directory is a variable defined in ‘mail-source.el’.
| Its value is "/home/asjo/Mail/incoming"
| Original value was "~/Mail/"
| 
|   You can customize this variable.
| 
| Documentation:
| Directory where incoming mail source files (if any) will be stored.
`----

You might also consider looking at this one:

,----[ C-h v mail-source-delete-incoming RET ]
| mail-source-delete-incoming is a variable defined in ‘mail-source.el’.
| Its value is 10
| 
|   You can customize this variable.
| 
| 
| This variable was introduced, or its default value was changed, in
| version 22.2 of Emacs.
| 
| Documentation:
| If non-nil, delete incoming files after handling.
| If t, delete immediately, if nil, never delete.  If a positive number, delete
| files older than number of days.
| 
| Removing of old files happens in ‘mail-source-callback’, i.e. no
| old incoming files will be deleted unless you receive new mail.
| You may also set this variable to nil and call
| ‘mail-source-delete-old-incoming’ interactively.
`----


  Best regards,

    Adam

-- 
 "It's the Disneyland-law                                   Adam Sjøgren
  So far out it makes anarchy a bore"                  asjo@koldfront.dk




  reply	other threads:[~2020-02-26 20:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-26 20:34 Florian Weimer
2020-02-26 20:50 ` Adam Sjøgren [this message]
2020-02-26 21:22   ` Florian Weimer

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=87v9ntxecg.fsf@tullinup.koldfront.dk \
    --to=asjo@koldfront.dk \
    --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).