Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: drafts from before starting gnus
Date: Thu, 13 Sep 2007 17:36:25 +0900	[thread overview]
Message-ID: <b4mabrr55di.fsf@jpl.org> (raw)
In-Reply-To: <873axjoo8m.fsf@jidanni.org>

>>>>> jidanni@jidanni.org wrote:

> If one is composing a message before starting gnus, upon starting gnus
> we are asked if we want to kill that message. We say no, and later we
> do C-C C-d and the file is saved to ~/Mail/drafts/*message*, but never
> appears in the drafts in the Group buffer. Easily forgotten.
> gnus-version "Gnus v5.11"

(defadvice message-set-auto-save-file-name (after make-it-gnus-draft activate)
  "Make it a draft that Gnus can handle even if Gnus is not running."
  (unless (gnus-alive-p)
    (setq message-draft-article (nndraft-request-associate-buffer "drafts"))))

I don't change message.el since I think making it behave like
this advice is a bad idea.



      reply	other threads:[~2007-09-13  8:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12 16:14 jidanni
2007-09-13  8:36 ` Katsumi Yamaoka [this message]

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=b4mabrr55di.fsf@jpl.org \
    --to=yamaoka@jpl.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).