Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Drafts and autosave
Date: 10 Nov 1998 05:35:10 +0100	[thread overview]
Message-ID: <m3hfw8jhc1.fsf@sparky.gnus.org> (raw)
In-Reply-To: Jan Vroonhof's message of "09 Nov 1998 15:10:04 +0100"

Jan Vroonhof <vroonhof@math.ethz.ch> writes:

> Well I'll be happy for anything that makes nndraft take notice of the
> autosaves. How to do it exactly is matter of taste.  If you do decide
> to scan for autosave files don't you have some problems when people
> have customized their autosaving (for instance in a seperate dir)?

That may be a problem.  Er...  Hm.  Perhaps saving the draft when
starting to edit a message is the way to go.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen


  reply	other threads:[~1998-11-10  4:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-30 10:37 Jan Vroonhof
1998-10-30 14:33 ` Colin Rafferty
1998-10-30 15:35   ` Jan Vroonhof
1998-10-30 15:55     ` Jan Vroonhof
1998-10-30 16:00     ` Colin Rafferty
1998-10-30 16:14       ` Dan Christensen
1998-10-31 14:20         ` Lars Magne Ingebrigtsen
1998-10-31 16:01           ` Jan Vroonhof
1998-10-31 16:24             ` Dan Christensen
1998-11-07 13:40             ` Lars Magne Ingebrigtsen
1998-11-07 16:59               ` Nelson Jose dos Santos Ferreira
1998-11-07 23:36                 ` Lars Magne Ingebrigtsen
1998-11-08  0:33                   ` Joev Dubach
1998-11-10  4:33                     ` Lars Magne Ingebrigtsen
1998-11-09 10:32                   ` Robert Bihlmeyer
1998-11-09 14:10               ` Jan Vroonhof
1998-11-10  4:35                 ` Lars Magne Ingebrigtsen [this message]
1998-11-10  8:59                   ` Nelson Jose dos Santos Ferreira
1998-11-13 17:52                     ` Lars Magne Ingebrigtsen
1998-11-16 12:13                       ` Jan Vroonhof
1998-10-31 15:47       ` Jan Vroonhof

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=m3hfw8jhc1.fsf@sparky.gnus.org \
    --to=larsi@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).