Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: Is this a buglet.. nndrafts:draft renegades
Date: Fri, 02 Nov 2001 13:29:20 -0800	[thread overview]
Message-ID: <m1y9loeua7.fsf@reader.newsguy.com> (raw)

I keep finding messages in nndraft:drafts that I didn't put there.
They get there by auto saving and gnus code I guess.  But if the
original message is killed (C-x k) before mailing and with having
never pressed C-x C-f or C-x C-d then that draft should die too right?

It doesn't under some circumstances.  Detailed here inside of just
such a message.  I started a composition then left it for a time with
C-x b.  Came back later, continued finally deciding to C-x k the whole
thing.

Next fetch I see a `1' light up nndrafts:draft . Take a look and
there is a partial copy of the killed messages.  It's detailed in the
file below (Some headers snipped to shorten it up)

C-x i t/killed_mail_message
======================================== 
  X-Draft-From: ("comp.editors" 38793)
  Newsgroups: comp.editors
  Subject: Re: Elvis 2.2f-beta is now available
  From: Harry Putnam <reader@newsguy.com>
  Date: Fri, 02 Nov 2001 11:35:12 -0800
  Message-ID: <m1zo65ezkf.fsf@reader.newsguy.com>
  --text follows this line--
  
  Starting this followup:
  Fri Nov  2 11:35:21 PST 2001
  
  I think I keep finding messages in nndraft:drafts that should not be
  there.  It works like this:
  Start a message of which this is an example.  Work on it for a while,
  then leave it temporarily for a while with C-x b *Group* or similar.
  
  Fri Nov  2 11:37:20 PST 2001
  Doing that very thing now
  
  ========================================
  
  Fri Nov 2 12:53:32 PST 2001 
  
  Here we is .. back about an hour and 20 min later.  Now I'm going to
  append-to-file this buffer then C-h k kill it.  Look in nndraft:drafts
  and see if something is there.  My feeling is there should not be.
  
  Waiting for auto save
  
  Fri Nov  2 12:55:49 PST 2001
  Auto save just occured appending then killing
  
  ......

Fri Nov  2 12:58:52 PST 2001

Look what I found in nndraft:drafts.
This shouldn't be here right?

========================================

  X-Draft-From: ("comp.editors" 38793)
  Newsgroups: comp.editors
  Subject: Re: Elvis 2.2f-beta is now available
  From: Harry Putnam <reader@newsguy.com>
  Date: Fri, 02 Nov 2001 11:35:12 -0800
  Message-ID: <m1zo65ezkf.fsf@reader.newsguy.com>
  
  
  Starting this followup:
  Fri Nov  2 11:35:21 PST 2001
  
  I think I keep finding messages in nndraft:drafts that should not be
  there.  It works like this:
  Start a message of which this is an example.  Work on it for a while,
  then leave it temporarily for a while with C-x b *Group* or similar.
  
  Fri Nov  2 11:37:20 PST 2001
  Doing that very thing now




             reply	other threads:[~2001-11-02 21:29 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-02 21:29 Harry Putnam [this message]
2001-11-02 21:46 ` Matt Armstrong
2001-11-03  1:06   ` Harry Putnam
2001-11-03 14:23     ` Per Abrahamsen
2001-11-03 20:29       ` Russ Allbery
2001-11-03  2:08   ` Russ Allbery
2001-11-03  3:01     ` Harry Putnam
2001-11-03  3:06     ` Karl Kleinpaste
2001-11-03  3:19       ` Samuel Padgett
2001-11-03 14:25         ` Per Abrahamsen
2001-11-03 14:56           ` ShengHuo ZHU
2001-11-03 15:54             ` Samuel Padgett
2001-11-03 19:32             ` Matt Armstrong
2001-11-03 21:10               ` Matt Armstrong
2001-11-03 22:25                 ` Samuel Padgett
2001-11-03 23:47                   ` Harry Putnam
2001-11-04  0:16                     ` Samuel Padgett
2001-11-04  1:17                       ` Harry Putnam
2001-11-04  1:47                         ` Samuel Padgett
2001-11-04  2:13                           ` Samuel Padgett
2001-11-03 23:40                 ` Harry Putnam
2001-11-05 10:53                   ` Per Abrahamsen
2001-11-05 16:22                     ` Harry Putnam
2001-11-05 17:30                       ` Samuel Padgett
2001-11-05 19:21                         ` Harry Putnam
2001-11-05 17:04                   ` Matt Armstrong
2001-11-05 17:26                     ` Samuel Padgett
2001-11-05 18:21                       ` Matt Armstrong
2001-11-06  9:29                         ` Per Abrahamsen
2001-11-06 14:05                           ` Samuel Padgett
2001-11-06 15:41                             ` Harry Putnam
2001-11-07 18:13                               ` Samuel Padgett
2001-11-07 19:03                                 ` Harry Putnam
2001-11-07 22:21                                   ` Samuel Padgett
2001-11-04 18:22                 ` Kai Großjohann
2001-11-04 18:31                   ` Samuel Padgett
2001-11-04 18:46                     ` Kai Großjohann
2001-11-04 19:20                     ` Matt Armstrong
2001-11-04 20:24                       ` Samuel Padgett
2001-11-05 17:06                         ` Paul Jarc
2001-11-05 17:19                           ` Matt Armstrong
2001-11-05 17:48                             ` Samuel Padgett
2001-11-05 17:22                           ` Samuel Padgett
2001-11-05 17:32                             ` Paul Jarc
2001-11-05 17:56                               ` Samuel Padgett
2001-11-03 15:40           ` Samuel Padgett
2001-11-03  3:56       ` Russ Allbery
2001-11-03 16:22         ` Kai Großjohann
2001-11-03 16:20     ` Kai Großjohann

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=m1y9loeua7.fsf@reader.newsguy.com \
    --to=reader@newsguy.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).