From: Bill Wohler <wohler@newt.com>
Subject: Re: Setting key bindings in view-mode-hook
Date: Sun, 27 Nov 2005 11:03:16 -0800 [thread overview]
Message-ID: <87d5klx6a3.fsf@olgas.newt.com> (raw)
In-Reply-To: DNEMKBNJBGPAOPIJOOICOEFKCPAA.drew.adams@oracle.com
"Drew Adams" <drew.adams@oracle.com> writes:
> I'd like to bind "q" in `view-mode' to `View-kill-and-leave'.
> I customized view-mode-hook with
>
> (lambda nil (local-set-key "q" (quote View-kill-and-leave)))
>
> However, "C-h c q" in a buffer in view mode still shows View-quit.
> What gives? How come my setting isn't honored?
> This is in recent CVS snapshot of Emacs 22, but a quick check reveals
> that this Emacs 21 shows the same behavior.
>
> It might help (I don't know) to look at my messages of 9/8/2005 and
> 9/9/2005, subject "quitting help buffer" (which are really about quitting
> view-mode).
Thanks. It helps since misery loves company.
> But that is not the behavior I get. For me, it iconifies the frame. And, in
> some (rarer) cases, it leaves the frame displayed (no change): `q' does
> nothing at all in those cases.
I'm not using frames. However, I tried view-file-other-frame and hit
`q'. I expected either the buffer or the frame to go away, but as you
said, it was iconified instead. Ew.
At best, I'd like `q' to kill the *Help* buffer or buffer in
view-mode. At worst, I'd like to bury it. But for me, `q' either does
nothing (maybe after visiting the *Help* buffer), or closes the window
but leaves the *Help* buffer in the #2 spot so a subsequent C-x b
takes me not to the mh-e.texi file that I was expecting but to *Help*.
I find that the use of `C' reliably does what I want (as well as C-x
k, of course). However, my fingers really prefer `q'. I think it's a
bug that I can't bind `q' to View-kill-and-leave.
I agree with you that all those ways of quitting view-mode are silly.
Once you're in view-mode, how you got there is immaterial. I want `q'
to do the same thing whether I ran view-mode manually, whether I'm in
a *Help* buffer, whether I ran `v' from dired, or have view-read-only
turned on. KISS. Perhaps you and I need to come up with recipes that
reliably show what we mean, but I would argue that if the exit path
were more simple, we wouldn't be here in the first place. Rather than
try to find and isolate a small bug, we should redesign and simplify
the exit path.
For example, I think view-mode should take the same design as
customize, in which there is a single function to exit
(Custom-buffer-done), bound to `q', which buries the buffer, unless
the option custom-buffer-done-kill is turned on, in which case the
buffer is killed.
However, I would agree that now is not the time to do this.
My 2c anyway.
--
Bill Wohler <wohler@newt.com> http://www.newt.com/wohler/ GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.
next prev parent reply other threads:[~2005-11-27 19:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-27 3:26 Setting key bindings in view-mode-hook Bill Wohler
2005-11-27 16:57 ` Drew Adams
2005-11-27 19:03 ` Bill Wohler [this message]
2005-11-27 19:36 ` Richard M. Stallman
2005-11-27 19:49 ` Bill Wohler
2005-11-28 4:46 ` Richard M. Stallman
2005-12-01 0:50 ` 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=87d5klx6a3.fsf@olgas.newt.com \
--to=wohler@newt.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).