Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: (unknown)
Date: Mon, 05 Nov 2001 07:25:22 -0800	[thread overview]
Message-ID: <m18zdlb5qh.fsf@totally-fudged-out-message-id> (raw)

Subject: Re: Is this a buglet.. nndrafts:draft renegades
References: <m1y9loeua7.fsf@reader.newsguy.com>
	<20011102214600.0ED71BD48@squeaker.lickey.com>
	<ylsnbw7gj8.fsf@windlord.stanford.edu>
	<vxkbsika6zo.fsf@cinnamon.vanillaknot.com>
	<E15zrLH-0001R4-00@harpo.homeip.net> <rjy9loc4ow.fsf@ssv2.dina.kvl.dk>
	<2nk7x7vr6n.fsf@zsh.cs.rochester.edu>
	<20011103193251.CBC04BD25@squeaker.lickey.com>
	<87ady3ef1u.fsf@squeaker.lickey.com>
	<m18zdn4e4d.fsf@reader.newsguy.com> <rjvggp8p51.fsf@ssv2.dina.kvl.dk>
From: Harry Putnam <reader@newsguy.com>
In-Reply-To: <rjvggp8p51.fsf@ssv2.dina.kvl.dk> (Per Abrahamsen's message of
 "Mon, 05 Nov 2001 11:53:46 +0100")
Date: Mon, 05 Nov 2001 07:24:38 -0800
Message-ID: <m1bsihb5qh.fsf@reader.newsguy.com>
User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.1 (i586-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Per Abrahamsen <abraham@dina.kvl.dk> writes:

> Harry Putnam <reader@newsguy.com> writes:
>
>> In the sense that a composition is a file, C-x k does kill the file
>> and data is lost in every other usage. 
>
> Does `C-x k' really any already generated autosave file?  If so, I
> agree it should do the same for composition buffers.  If not, I
> believe it shouldn't do it for composition buffers either.

M-x cd 
test_dir <RET>

C-x C-f tnew

Type:
Testing the action of C-x k on new composition buffer of tnew
before an auto-save has occured
<C-x k yes>

C-x d <RET> (gone without a trace)

Type:
Testing the action of C-x k on new composition buffer of tnew
after an auto-save has occured
<waiting>
excerpt from *Nessages*
        Auto-saving...done

<C-x k yes>

C-x d <RET> g 
(cong without a trace)

That is the behavior I see.  And I agree that a new message
composition should behave the same.



             reply	other threads:[~2001-11-05 15:25 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-05 15:25 Harry Putnam [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-09-17 20:35 Bob Newell
2021-09-18  6:15 ` (unknown) Andreas Schwab
2006-07-29 14:11 (unknown) Daiki Ueno
2003-04-02  5:43 (unknown) Ben Brown
2003-01-21  2:44 (unknown) Jason L Tibbitts III
2002-10-20 20:14 (unknown) Unknown
2002-05-10 20:40 (unknown) joseph edward
2002-05-09  4:49 (unknown) laurent mpeti kabila
2002-05-07  6:06 (unknown) laurent mpeti kabila
2002-05-03 15:51 (unknown) laurent mpeti kabila
2002-01-21  5:19 (unknown) Ä£±¸¿¡°Ô
2001-12-09  3:15 (unknown) Harry Putnam
2001-11-11 17:39 (unknown) owner-ding
2001-11-04 18:05 (unknown) Harry Putnam
2001-11-02  8:06 (unknown) BALABAN ADRIAN
2001-04-03 17:25 (unknown) Harry Putnam
2000-12-13 15:18 (unknown) colman
2000-10-09  9:20 (unknown) Umesh Biradar
2000-08-15 15:32 (unknown) Abuse
1999-04-19 16:15 (unknown) karthy
1998-11-29 23:54 (unknown) Jason L Tibbitts III
1998-10-17  6:59 (unknown) Mark Hovey
1998-10-15 16:32 (unknown) Mark Hovey
1998-10-15 15:29 (unknown) Mark Hovey
1998-09-19 15:34 (unknown) Michael Harnois
1997-06-08  2:23 (unknown) anonymous
1997-03-26 14:37 (unknown) Thomas Bopp
1996-11-28  1:50 (unknown) lars
1996-08-19  5:16 (unknown) Michael Harnois
1996-02-21 23:26 (unknown) Steven L. Baur
1996-02-21 23:06 (unknown) Steven L. Baur

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=m18zdlb5qh.fsf@totally-fudged-out-message-id \
    --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).