From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: Getting rid of `Incoming*' stuff
Date: 09 Feb 1999 13:09:55 -0500 [thread overview]
Message-ID: <ltlni75tzg.fsf@asfast.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "09 Feb 1999 19:04:16 +0100"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Lloyd Zusman <ljz@asfast.com> writes:
>
> > It also would be nice, in my opinion, if there was a way to specify an
> > alternate directory for the incoming files, other than the mail
> > directory. I didn't see anything in the code to handle this. Perhaps
> > we need a `mail-source-incoming-directory' variable?
>
> `mail-source-directory'.
But that would put the incoming files in the top-level directory of
the mail source directory tree, which contains lots of other stuff.
I'd like to send those files to a completely different location. I
used to be able to do this prior to the `mail-source-*' changes.
--
Lloyd Zusman
ljz@asfast.com
next prev parent reply other threads:[~1999-02-09 18:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-09 17:23 Stefan Waldherr
1999-02-09 17:38 ` Lars Magne Ingebrigtsen
[not found] ` <m3u2wvxy1x.fsf@peorth.gweep.net>
1999-02-09 17:59 ` Lloyd Zusman
1999-02-09 18:04 ` Lars Magne Ingebrigtsen
1999-02-09 18:09 ` Lloyd Zusman [this message]
1999-02-09 19:02 ` Lars Magne Ingebrigtsen
1999-02-09 18:01 ` Karl Kleinpaste
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=ltlni75tzg.fsf@asfast.com \
--to=ljz@asfast.com \
/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).