From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Ergus <spacibba@aol.com>
Cc: emacs-devel@gnu.org
Subject: Re: Quit and Close Emacs Special Windows
Date: Tue, 30 Jun 2020 13:04:57 -0400 [thread overview]
Message-ID: <jwv5zb8zdud.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87ftaej5pp.fsf@ergus.i-did-not-set--mail-host-address--so-tickle-me> (Ergus's message of "Mon, 29 Jun 2020 16:40:23 +0200")
> I have been reading this site:
>
> https://christiantietze.de/posts/2019/10/emacs-quit-special-windows/
>
> and I am wondering why we don't provide an option to enable this
> behaviour by default in some cases without needing the "hack" in the
> link. It doesn't seems to be too complex to implement right?
What do you mean by "this behavior"?
I just tried
emacs -Q
M-x compile
..select the compilation window...
q
and sure enough I was back to a single-window setup.
So, IIUC we already provide "this behavior".
> I know it is just a detail, but in some cases (like when using man or
> compile mode, or reading a function documentation, or after executing
> magit commands) it doesn't make sense to keep the buffer in the buffer
> list after pressing q in 90% of the times.
I don't understand the connection with the previous paragraph.
Stefan
next prev parent reply other threads:[~2020-06-30 17:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ftaej5pp.fsf.ref@ergus.i-did-not-set--mail-host-address--so-tickle-me>
2020-06-29 14:40 ` Quit and Close Emacs Special Windows Ergus
2020-06-29 15:09 ` Drew Adams
2020-06-29 16:13 ` Yuan Fu
2020-06-29 16:45 ` Ergus
2020-06-29 17:00 ` Drew Adams
2020-06-29 17:22 ` Ergus
2020-06-30 2:44 ` Stefan Monnier
2020-06-30 3:24 ` Drew Adams
2020-06-30 4:27 ` Stefan Monnier
2020-06-30 15:39 ` Drew Adams
2020-06-30 17:04 ` Stefan Monnier [this message]
2020-07-01 1:31 ` Ergus
2020-07-01 3:47 ` Yuan Fu
2020-07-01 13:55 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv5zb8zdud.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=spacibba@aol.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.