From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: sending a draft message
Date: Thu, 12 May 2005 13:49:33 -0400 [thread overview]
Message-ID: <vxkbr7gtjv6.fsf@mesquite.charcoal.com> (raw)
In-Reply-To: <x02m4qd8s5uk.fsf@lochnagar.ph.ed.ac.uk>
Philip Clark <P.J.Clark@ed.ac.uk> writes:
> I try to send it with Ctrl c c. However, this just seems to save a
> new version of the draft and doesn't actually send it.
Once you have used `D e', you should have the message in an ordinary
"*message*" buffer. `C-c C-c' should certainly send it.
What does `C-h c C-c C-c' report? It should identify that key
sequence as message-send-and-exit.
As a stopgap, if it is truly merely saving new drafts without sending,
try `D s' in the drafts group to send it.
next prev parent reply other threads:[~2005-05-12 17:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 17:37 Philip Clark
2005-05-12 17:49 ` Karl Kleinpaste [this message]
2005-05-12 18:10 ` Philip Clark
2005-05-13 12:01 ` Phillip Lord
2005-05-13 13:35 ` johnsu01
2005-05-13 21:20 ` Philip Clark
2005-05-13 23:53 ` johnsu01
2005-05-12 17:56 ` Andrew Raines
2005-05-12 18:08 ` Philip Clark
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=vxkbr7gtjv6.fsf@mesquite.charcoal.com \
--to=karl@charcoal.com \
--cc=karl+usenet@charcoal.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).