unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Keybinding nit
Date: Fri, 20 Oct 2006 09:43:00 +0200	[thread overview]
Message-ID: <85d58nph4r.fsf@lola.goethe.zz> (raw)
In-Reply-To: <45386168.8060700@swipnet.se> (Jan D.'s message of "Fri\, 20 Oct 2006 07\:40\:56 +0200")

"Jan D." <jan.h.d@swipnet.se> writes:

> David Kastrup skrev:
>> Richard Stallman <rms@gnu.org> writes:
>> 
>>>     C-x 4 0 and C-x 5 0 are not at all symmetric, and C-x 4 0 is not
>>>     really intuitive.
>>>
>>>     Maybe one should rather have C-x 4 k and C-x 5 k for killing both
>>>     buffer and window/frame?
>>>
>>> Since C-x k reads a buffer name, I would expect C-x 4 k to
>>> read a buffer name also.
>> 
>> Well, I wouldn't (there are quite a few keybindings where "k" just
>> kills something).  And since neither C-x 0 nor C-x 5 0 kills a buffer,
>> I would not expect C-x 4 0 to do it, either.
>> 
>> It all boils down to what feels more natural and expected.  Of course
>> that is a matter of personal taste, and I like to think my taste is
>> not too far out here.  Other opinions?
>
> I think changing C-x 4 0 to just kill the window and adding C-x 4 k to kill
> buffer and window makes sense.
>
> But I have a question for C-x 5 k.  If you have more than one window
> showing different buffers in the frame, shall it kill all the
> buffers, or prompt for the one to kill?  I'd assume the latter.  The
> prompt could be skipped if there is just one buffer shown in that
> frame.

Good catch.  I'd just kill the selected window of the frame.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2006-10-20  7:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18 15:37 Keybinding nit David Kastrup
2006-10-18 18:29 ` Peter Lee
2006-10-18 23:22   ` Miles Bader
2006-10-19 16:53     ` Kevin Rodgers
2006-10-23  1:43       ` Miles Bader
2006-10-24 22:11         ` Kevin Rodgers
2006-10-24 23:29           ` Miles Bader
2006-10-25 21:38             ` Kevin Rodgers
2006-10-19 12:56 ` Richard Stallman
2006-10-19 13:07   ` David Kastrup
2006-10-19 20:06     ` Nick Roberts
2006-10-19 20:46       ` David Kastrup
2006-10-19 21:19         ` Nick Roberts
2006-10-19 21:37           ` David Kastrup
2006-10-20 16:09         ` Stuart D. Herring
2006-10-20  5:40     ` Jan D.
2006-10-20  7:43       ` David Kastrup [this message]
2006-10-20 19:13         ` Drew Adams

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=85d58nph4r.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).