From: Samuel Padgett <spadgett1@nc.rr.com>
Cc: ding@gnus.org
Subject: Re: Is this a buglet.. nndrafts:draft renegades
Date: Sun, 04 Nov 2001 15:24:54 -0500 [thread overview]
Message-ID: <87ady2qo6h.fsf@harpo.homeip.net> (raw)
In-Reply-To: <87668qibri.fsf@squeaker.lickey.com> ("Matt Armstrong"'s message of "Sun, 04 Nov 2001 12:20:17 -0700")
"Matt Armstrong" <matt+dated+1007493620.315b12@lickey.com> writes:
> Samuel Padgett <spadgett1@nc.rr.com> writes:
>
>> But what if I accidentally kill a buffer while composing a message I
>> haven't saved? There would be no way to recover the message.
>
> Emacs will prompt you with "Buffer X modified; kill anyway?" -- I
> think that is good enough.
No, I disagree. If I do this to a C source file, I can always recover
my changes using the autosave file. But I can't now with a message I
was composing? Why?
I usually don't worry too much when I'm asked the "Buffer modified;
kill anyway?" question because I know Emacs will always kindly leave
an autosave file for me just in case I'm doing something boneheaded.
C-x k is a global command. Changing its meaning in message-mode--and
making it more destructive to boot--is a bad idea.
Maybe changing C-c C-k to delete the autosave file is OK, though. I
wonder if anyone relies on the current behavior?
Sam
next prev parent reply other threads:[~2001-11-04 20:24 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
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 [this message]
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=87ady2qo6h.fsf@harpo.homeip.net \
--to=spadgett1@nc.rr.com \
--cc=ding@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).