unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sam Steingold <sds@gnu.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 12311@debbugs.gnu.org
Subject: bug#12311: (special-mode-map): Delete binding for `z'.
Date: Sun, 02 Sep 2012 01:19:52 -0400	[thread overview]
Message-ID: <87fw712e87.fsf__1659.54782064563$1346563247$gmane$org@gnu.org> (raw)
In-Reply-To: <363C856A8EDB4545897D760AD952E828@us.oracle.com> (Drew Adams's message of "Sat, 1 Sep 2012 19:38:28 -0700")

The following message is a courtesy copy of an article
that has been posted to gmane.emacs.devel as well.

> * Drew Adams <qerj.nqnzf@benpyr.pbz> [2012-09-01 19:38:28 -0700]:
>
>> I use this all the time in buffers like *Help*, 
>
> Why bother to kill *Help*?  Why do that rather than `q'?

because 'q' will eventually start showing old *Help* buffers.
because 'q' deletes the window which I want to keep.

>> *Dired* &c.  What am I supposed to use instead? C-u q?
>
> Sure, why not?  Or `q' if you don't need to kill it.

because C-u q is two keystrokes; quite often I keep hitting 'z' until I
get to a buffer where z self-inserts.

> Or `C-x v' if you want to replace it.

C-x v is the vc prefix for me.

> You want to kill Dired but you don't want to use `C-u q'.
> OK, so bind `z' to killing once again if you want to.

the question is whether this is a generally useful binding.
I think it is.

> Or is it about other special-mode buffers?  That's the useful question, to me.
> I would say forget about *Help* (which doesn't need to be killed) and Dired
> (which you sometimes don't want to kill).
>
> But are there special-mode buffers where `z' killing the buffer is really
> useful?  If so, then maybe the fix was too heavy-handed.

I don't think special-mode buffers are "precious" - they are easily
restored, so killing them accidentally should not be a problem.
Apparently others disagree.

>> How is a ding more valuable than a useful behavior?
>
> Killing the buffer is not the only or the most useful behavior `z'
> could have in Dired.  Dired is a rich mode with lots of keys already
> taken and with plenty of commands that could be bound to keys.

So bind it in dired mode. The change affects all the other special modes!


-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 12.04 (precise) X 11.0.11103000
http://www.childpsy.net/ http://dhimmi.com http://truepeace.org
http://think-israel.org http://pmw.org.il http://mideasttruth.com
Do the arithmetic or be doomed to talk nonsense. --John McCarthy





       reply	other threads:[~2012-09-02  5:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87oblp2nfr.fsf@gnu.org>
     [not found] ` <363C856A8EDB4545897D760AD952E828@us.oracle.com>
2012-09-02  5:19   ` Sam Steingold [this message]
     [not found]   ` <87fw712e87.fsf@gnu.org>
2012-09-02 13:39     ` bug#12311: (special-mode-map): Delete binding for `z' Drew Adams
2012-09-03  8:09     ` Chong Yidong

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='87fw712e87.fsf__1659.54782064563$1346563247$gmane$org@gnu.org' \
    --to=sds@gnu.org \
    --cc=12311@debbugs.gnu.org \
    --cc=drew.adams@oracle.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.
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).