From: "Drew Adams" <drew.adams@oracle.com>
Subject: quitting help buffer
Date: Thu, 8 Sep 2005 20:56:55 -0700 [thread overview]
Message-ID: <MEEKKIABFKKDFJMPIOEBMEMOCMAA.drew.adams@oracle.com> (raw)
I cannot figure out how to make `q' do what it used to do in Emacs 20, to
quit the *Help* buffer.
I use non-nil `pop-up-frames'. I want `q' to do the equivalent of
`quit-window'. In my context, that will kill the buffer and delete its frame
(thanks to my redefining `delete-window' to DTRT for one-window
pop-up-frames). Bye; good riddance.
I don't want `q' to iconify the frame, slip it in my back pocket, mail it to
me, or do any of the other strange and wonderful things I see advertised in
the doc for `view-mode'. How can I get `q' to do something as simple as kill
the buffer and delete its window (frame)?
BTW, I find the doc string for view-mode difficult to understand wrt the
various quitting scenarios. It doesn't help that there are multiple
similarly named commands that use synonyms for "quit" as their only
distinction:
View-quit
View-exit
View-exit-and-edit
View-quit-all
View-leave
View-kill-and-leave
What is this? The variations don't tell us anything in particular about what
the functions do - there is no significant difference between the words
"quit", "exit", and "leave".
Why not also
View-split, -give-up, -depart, -drop-out, -relinguish, -throw-in-the-towel,
-take-leave, -go-away, -go-out, -get-out, -pull-up-stakes, and -escape? Or
are those variants being saved for Emacs 23? Not to mention combinations of
these with possible subsequent
actions: -and-kill, -and-pass-out, -and-hang-around, -and-go-down-to-the-poo
l-hall,...
Could this be a sign that something is wrong in the design? Isn't it a bit
bizarre for a command to spend so much effort trying to deal with all of the
possible ways and contexts in which it might be called (used)? Shouldn't
such concerns be for the callers and not the callee? This seems bass
ackwards, to me.
next reply other threads:[~2005-09-09 3:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 3:56 Drew Adams [this message]
2005-09-09 12:50 ` quitting help buffer Richard M. Stallman
2005-09-09 16:05 ` Drew Adams
2005-09-10 8:14 ` Richard M. Stallman
2005-12-01 0:44 ` view mode: `q' does not delete frame Drew Adams
2005-12-01 1:16 ` Drew Adams
2005-12-01 20:42 ` Eli Zaretskii
2005-12-02 1:57 ` Drew Adams
2005-12-03 9:55 ` Eli Zaretskii
2005-12-03 15:08 ` Stefan Monnier
2005-12-03 15:37 ` Drew Adams
2005-12-03 21:35 ` Stefan Monnier
2005-12-03 22:46 ` Drew Adams
2005-12-02 18:21 ` Richard M. Stallman
2005-12-03 12:08 ` Eli Zaretskii
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=MEEKKIABFKKDFJMPIOEBMEMOCMAA.drew.adams@oracle.com \
--to=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).