From: Drew Adams <drew.adams@oracle.com>
To: Peter <peter.milliken@gmail.com>, help-gnu-emacs@gnu.org
Subject: RE: Should delete-window switch to next buffer when there is only one window?
Date: Tue, 14 Jan 2014 15:33:26 -0800 (PST) [thread overview]
Message-ID: <58204764-31df-4d07-8e48-30952afebb9f@default> (raw)
In-Reply-To: <64e2823c-29c6-4874-b9a2-6dfa6eda4c4a@googlegroups.com>
> No, I think it is doing the right thing. It doesn't make any sense
> for YOUR code to delete the only window that exists. If it just
> switched buffers (to what? what rule should apply in this case? A
> random buffer selection?) then it isn't doing what you requested -
> which is to delete the window.
>
> I think a bit more thought on your side should be applied rather
> than suggesting that Emacs behaviour change to suit you.
Put it another way, perhaps: Define your own command (i.e., with a
different name), and remap `delete-window' to your command, for
(your own) interactive use.
Two points are important here:
1. `delete-window' is an Emacs function used in many places. It
is not just a command, and it is not invoked only interactively
(e.g., via `C-x 0').
2. Try it out on yourself before suggesting that Emacs adopt it.
Use it for a while (months? years?).
These are two things to keep in mind whenever you have an idea
about changing the default behavior of some command.
next prev parent reply other threads:[~2014-01-14 23:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.11954.1389738686.10748.help-gnu-emacs@gnu.org>
2014-01-14 22:40 ` Should delete-window switch to next buffer when there is only one window? Emanuel Berg
2014-01-14 22:43 ` Emanuel Berg
2014-01-14 23:16 ` Peter
2014-01-14 23:32 ` Emanuel Berg
2014-01-15 8:39 ` Marcin Borkowski
2014-01-14 23:33 ` Drew Adams [this message]
2014-01-15 1:19 ` Ernest Adrogué
2014-01-15 5:12 ` Thien-Thi Nguyen
[not found] ` <mailman.11970.1389762517.10748.help-gnu-emacs@gnu.org>
2014-01-15 21:13 ` Emanuel Berg
2014-01-14 22:30 Ernest Adrogué
2014-01-14 23:57 ` Drew Adams
2014-01-15 8:45 ` Marcin Borkowski
2014-01-15 13:31 ` Stefan Monnier
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=58204764-31df-4d07-8e48-30952afebb9f@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=peter.milliken@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).