From: Nat Makarevitch <nat@makarevitch.org>
To: ding@gnus.org
Subject: Re: Getting rid of the Fcc: field, and other compose problems.
Date: Sun, 5 May 2013 21:44:26 +0000 (UTC) [thread overview]
Message-ID: <loom.20130505T234238-351@post.gmane.org> (raw)
In-Reply-To: <87sjo7rn3v.fsf@topper.koldfront.dk>
Adam Sjøgren <asjo <at> koldfront.dk> writes:
> On Thu, 08 Sep 2011 14:59:36 +0530, G wrote:
Old one...
> > 1. The "Fcc:" field is populated with a non-existant directory, and I am
> > prompted whether I want to create this maildir.
Same problem here (Debian). It was tied to "notmuch" and (setq notmuch-fcc-
dirs nil) fixed it.
next prev parent reply other threads:[~2013-05-05 21:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 9:29 G Philip
2011-09-08 16:54 ` Adam Sjøgren
2011-09-08 18:56 ` gphilip
2011-09-08 19:07 ` Adam Sjøgren
2011-09-08 21:04 ` Richard Riley
2011-09-09 7:51 ` G Philip
2011-09-10 19:55 ` Lars Magne Ingebrigtsen
2013-05-05 21:44 ` Nat Makarevitch [this message]
[not found] <loom.20110908T115419-459@post.gmane.org>
2011-09-08 10:38 ` Eric S Fraga
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=loom.20130505T234238-351@post.gmane.org \
--to=nat@makarevitch.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).