From: Ergus <spacibba@aol.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: Re: Quit and Close Emacs Special Windows
Date: Mon, 29 Jun 2020 19:22:47 +0200 [thread overview]
Message-ID: <20200629172230.mpm4ahvj2wm7ak5k@ergus> (raw)
In-Reply-To: <f9f1c135-5cc7-4e45-9c4c-8f332f8db4f3@default>
On Mon, Jun 29, 2020 at 05:00:01PM +0000, Drew Adams wrote:
>
>No idea; sorry. I'm just saying what I do.
>
>The definition of `quit-window-delete' that I use
>has this comment:
>
> ;; Candidate as a replacement for `quit-window',
> ;; at least when used interactively. For example:
> ;; (define-key global-map [remap quit-window] 'quit-window-delete)
> ;;
> ;; Thanks to Martin Rudalics for suggestions.
>
>Someone else will need to make changes to Emacs, if
>such is decided.
>
>The things I mentioned don't necessarily belong
>together for others. For me they make sense together.
>
>For example, making buffers `*...*' special-display
>is unrelated to quitting help buffers with `q'.
>
I tried your code for making buffers `*...*' special-display and as I
only use -nw the behavior is not good. The first time I call commands
like `man' nothing happens in the front but the buffer starts in the
backend.
In gui the behavior is fine as expected.
>But for me it makes sense. I show all such buffers
>in their own dedicated window (frame, in fact), and
>when I use `q' to quit the buffer I want to delete
>the frame. I imagine that at least some others won't
>want such behavior.
>
>Do I think that it would be good to have a simple way
>to get `q' to delete the window? Yes. Do I think it
>would be good to have a simple way for `q' to delete
>a one-window frame? Yes. But someone else will need
>to think about and decide whether that's helpful in
>general and, if so, what's the best way to offer it.
I think that with a simple variable and an `or` in the condition will be
good enough (something like quit-always-kill or so).
The only corned case I can imagine so far is the case where quit-window
is not called from `q' in not *...* buffers. But I don't know if that
even happen.
Hopefully someone will come with a better solution...
Best,
Ergus.
next prev parent reply other threads:[~2020-06-29 17:22 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 [this message]
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
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=20200629172230.mpm4ahvj2wm7ak5k@ergus \
--to=spacibba@aol.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
/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).