From: Harry Putnam <reader@newsguy.com>
Subject: Re: Is this a buglet.. nndrafts:draft renegades
Date: Sat, 03 Nov 2001 15:40:50 -0800 [thread overview]
Message-ID: <m18zdn4e4d.fsf@reader.newsguy.com> (raw)
In-Reply-To: <87ady3ef1u.fsf@squeaker.lickey.com> ("Matt Armstrong"'s message of "Sat, 03 Nov 2001 14:10:37 -0700")
"Matt Armstrong" <matt+dated+1007413841.964140@lickey.com> writes:
[...]
> Actually, I reverse my opinion. C-x k deletes a buffer, not a file.
>
> I have C-x C-s C-x k deeply ingrained in my muscle memory -- it is the
> "save to disk, then delete buffer" key sequence. Data does not get
> lost when doing this.
In the sense that a composition is a file, C-x k does kill the file
and data is lost in every other usage. However it does prompt for the
permission.
The sequence below assumes `file' does not yet exist. Just like a
fresh composition buffer.
C-x C-f file
type Start
C-x k prompt: yes
The file is removed and data is lost. Why should a composition
buffer be any different?
>
> If C-x k suddenly deletes the message out of the drafts folder, I'll
> end up accidentally deleting drafts left and right.
Why is this so perilous compared to behavior on a not existent file in
C-x C-f file?
> I'd be fine if message buffers prompted me "delete message from drafts
> folder too?" when they were killed. Or we could provide a "kill this
> message buffer and its draft" key binding.
Currently C-x k does prompt for permission to continue. Maybe you
have it turned off.
In this buffer I press C-x k and get:
Kill buffer: (default *wide reply to Matt Armstrong*)
Do you need more than that?
next prev parent reply other threads:[~2001-11-03 23:40 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 [this message]
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=m18zdn4e4d.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).