From: Harry Putnam <reader@newsguy.com>
Subject: Re: Is this a buglet.. nndrafts:draft renegades
Date: Sat, 03 Nov 2001 17:17:10 -0800 [thread overview]
Message-ID: <m1ofmj2v3d.fsf@reader.newsguy.com> (raw)
In-Reply-To: <E160AxH-0002ls-00@harpo.homeip.net> (Samuel Padgett's message of "Sat, 03 Nov 2001 19:16:03 -0500")
Samuel Padgett <spadgett1@nc.rr.com> writes:
[...]
> Hm. If I compose a message from the *Group* buffer using "m" and then
> type "C-c C-k" midway through, it is put in my drafts folder. Is this
> not what you see?
>
>> I guess that is what I should be using. I still think C-x k should
>> do it to... to be consisitent.
> This would be _inconsistent_ with the way C-x k works in the rest of
> Emacs. I only think the message should not go to the drafts folder
How so? m in gnus opens a fresh composition buffer where none was
before. C-x k here and it lingers in drafts.
C-x C-f can open a file where none existed before and present you with
a composition buffer. If you use C-x k here it all dies. It doesn't
linger somewhere.
I was saying C-x k should be the same in gnus as everywhere else. In
fact it was.
> after C-x k if it's unmodified and hasn't been saved. After all,
> isn't this what C-c C-k is for: to cancel the message without making
> it a draft? And if this is not what C-c C-k is for, why have both C-c
> C-k and C-c C-d?
Yeah, I think I just need to switch to using C-c C-k. Just my habit
is C-x k which has always worked until recently.
next prev parent reply other threads:[~2001-11-04 1:17 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 [this message]
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=m1ofmj2v3d.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).