From: Lloyd Zusman <ljz@asfast.com>
Subject: Recommended way to force a posted article into drafts?
Date: 07 May 2000 20:11:28 -0400 [thread overview]
Message-ID: <ltvh0pew9b.fsf@asfast.com> (raw)
I'm using the latest (or near-latest) CVS version of gnus.
In certain newsgroups, I want to be able to review and revise all of
my articles before they actually get posted. In these special groups,
I map `\C-c \C-c' to my special function for deferring the post. What
this function does is to simply force the article into my `drafts'
folder. `\C-c \C-c' remains mapped to `message-send-and-exit' in all
the other groups (including `drafts').
My question is this: is the following function the recommended method
for forcing an article into `drafts'? (this is a stripped-down version
of my actual function, showing only the essentials):
(my-defer-posting ()
(save-article)
(kill-buffer (current-buffer)))
This seems to work just fine and is consistent with how drafts work in
general ... but just in case, I want to double-check in case there's
something special that I should do in addition to this or instead of
this.
Thanks in advance.
--
Lloyd Zusman
ljz@asfast.com
next reply other threads:[~2000-05-08 0:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-08 0:11 Lloyd Zusman [this message]
2000-05-08 0:21 ` Shenghuo ZHU
2000-05-08 0:34 ` Lloyd Zusman
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=ltvh0pew9b.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).