From: Seb <spluque@gmail.com>
To: ding@gnus.org
Subject: Re: message-dont-send kill buffer
Date: Fri, 07 Nov 2008 21:37:46 -0600 [thread overview]
Message-ID: <87vduyopkl.fsf@patagonia.sebmags.homelinux.org> (raw)
In-Reply-To: <871vxormy7.fsf@thinkpad.tsdh.de>
On Fri, 07 Nov 2008 08:53:52 +0100,
Tassilo Horn <tassilo@member.fsf.org> wrote:
[...]
> But that works only after a message beeing sent, not for drafted
> messages.
> In your situation I'd use `C-x C-s' (save-buffer) which will draft the
> message, too, but won't bury the buffer. Then you can kill it with
> `C-x k'.
I was looking at message-postpone-actions, which seems more appropriate,
and tried:
(message-add-action
`(kill-buffer)
'postpone)
but the buffer remains, so I'm not doing this correctly. Any help on
doing a message-add-action on 'postpone so that the mail buffer is
killed without removing the draft message? Thanks.
--
Seb
next prev parent reply other threads:[~2008-11-08 3:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 3:59 Seb
2008-11-07 7:53 ` Tassilo Horn
2008-11-08 3:37 ` Seb [this message]
2008-11-16 23:43 ` Seb
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=87vduyopkl.fsf@patagonia.sebmags.homelinux.org \
--to=spluque@gmail.com \
--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).