From: Harry Putnam <reader@newsguy.com>
Subject: Re: Is this a buglet.. nndrafts:draft renegades
Date: Mon, 05 Nov 2001 08:22:08 -0800 [thread overview]
Message-ID: <m1lmhl89xr.fsf@reader.newsguy.com> (raw)
In-Reply-To: <rjvggp8p51.fsf@ssv2.dina.kvl.dk> (Per Abrahamsen's message of "Mon, 05 Nov 2001 11:53:46 +0100")
[ NOTE sorry if this proves to be redundant but somehow I am getting
an unusual behavior here. Posted a message just like this one a few
minutes ago but it appeared in an unexpected format on ding.
See Message-ID: <m18zdlb5qh.fsf@totally-fudged-out-message-id>
(I think Samuel or someone already posted on this and its cvs cured
problem I hope.... I'll be cvs updating shortly)]
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.
next prev parent reply other threads:[~2001-11-05 16:22 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-02 21:29 Harry Putnam
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 [this message]
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=m1lmhl89xr.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).