Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Keep losing work in non-file-visiting buffers
Date: Fri, 05 Dec 2003 00:05:52 GMT	[thread overview]
Message-ID: <jwvad68dtl5.fsf-monnier+gnu.emacs.gnus__38240.2657335207$1138669431$gmane$org@vor.iro.umontreal.ca> (raw)
In-Reply-To: <m3fzg0rwa3.fsf@defun.localdomain>

>> Good point.  I suffer from something similar with Gnus message buffers
>> getting lost when my Emacs crashes (or my network connection goes down).
>> Does anyone know how to make them autosave into the drafts buffer

> This seems to be the default in Gnus 5.10 -- in this Message buffer I get:

> ,----[ C-h v buffer-auto-save-file-name RET ]
> | buffer-auto-save-file-name's value is 
> | "/home/harder/News/drafts/drafts/#31#"

But does it actually get auto-saved ?  I have pretty much the same value
as you do (with Gnus-5.9 from Emacs-CVS) but nothing gets saved: neither
drafts/#31# nor drafts/31.

Oh, I see it now: it only gets saved if I make modifications.
So I just need to get Emacs to mark the buffer as modified from the start
and it will get saved.  Good.

Now on to the next step: how do I make it so that #31# is listed in
the nndrafts:drafts folder ?

You see, I'd like to be able to hit `F' or `R' on messages to which I want
to reply and be sure that this will be remembered in nndrafts:drafts in case
I forget to reply and leave Emacs (willfully or not).


        Stefan


           reply	other threads:[~2003-12-05  0:05 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <m3fzg0rwa3.fsf@defun.localdomain>]

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='jwvad68dtl5.fsf-monnier+gnu.emacs.gnus__38240.2657335207$1138669431$gmane$org@vor.iro.umontreal.ca' \
    --to=monnier@iro.umontreal.ca \
    /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).