unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ergus <spacibba@aol.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Quit and Close Emacs Special Windows
Date: Wed, 01 Jul 2020 03:31:10 +0200	[thread overview]
Message-ID: <6612E345-621D-4453-AE61-01E757B08765@aol.com> (raw)
In-Reply-To: <jwv5zb8zdud.fsf-monnier+emacs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1654 bytes --]

Hi Stefan:

As "this behavior" I mean that pressing q effectively closes the buffer instead of keeping it around in the buffer list. When working in big projects with too many files usually there are too many *-...-* buffers (magit, compile, man, logs...). And the user needs to keep closing them constantly (with C-u q or explicitly)
This is not only annoying some times (for example for rotating buffers with C-x right) but also is somehow unnatural for term users who are used to call ex. man from the terminal and quit quickly to continue.

On June 30, 2020 7:04:57 PM GMT+02:00, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> 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

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[-- Attachment #2: Type: text/html, Size: 2273 bytes --]

  reply	other threads:[~2020-07-01  1:31 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
2020-07-01  1:31     ` Ergus [this message]
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

  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=6612E345-621D-4453-AE61-01E757B08765@aol.com \
    --to=spacibba@aol.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).