From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: 64619@debbugs.gnu.org, philipk@posteo.net, sbaugh@janestreet.com,
sbaugh@catern.com, rudalics@gmx.at, drew.adams@oracle.com
Subject: bug#64619: [PATCH] Add toggle-window-dedicated command
Date: Sun, 20 Aug 2023 09:13:24 +0300 [thread overview]
Message-ID: <83edjyxmuz.fsf@gnu.org> (raw)
In-Reply-To: <387ee04aa9572975a3cd@heytings.org> (message from Gregory Heytings on Sat, 19 Aug 2023 22:36:45 +0000)
> Date: Sat, 19 Aug 2023 22:36:45 +0000
> From: Gregory Heytings <gregory@heytings.org>
> cc: Spencer Baugh <sbaugh@janestreet.com>,
> Philip Kaludercic <philipk@posteo.net>, 64619@debbugs.gnu.org,
> martin rudalics <rudalics@gmx.at>, Eli Zaretskii <eliz@gnu.org>,
> Drew Adams <drew.adams@oracle.com>
>
>
> >
> > In fact, I initially used strong dedication in my patch. But I found it
> > annoying that I had to turn off strong dedication explicitly if I wanted
> > to switch to another buffer. That's what made me realize that weak
> > dedication was better.
> >
>
> It's not annoying, it's what dedication is for. It's not more annoying
> than using C-x C-q in a buffer, and later typing something in that buffer
> and realizing (with a similar error message) that it doesn't work: you get
> what you asked.
>
> >
> > But C-x b doesn't use display buffer, and instead just errors when the
> > current window is strongly dedicated, which I think is fairly useless
> > behavior; the user reaction is almost always going to be annoyance
> > followed by C-x w d and C-x b again. So I think weak dedication is
> > better.
> >
>
> If you think that's annoying, then I'd suggest setting the
> switch-to-buffer-in-dedicated-window configuration option. It's there for
> a reason, and you can select between no less than four behaviors: one of
> them is likely the one you want.
I think the reason that people disagree about the details is because
they have different use cases for this feature in mind.
To reconcile these two opinions, we could introduce a user option
which would invert the default: make strongly-dedicated the default
and weekly-dedicated the optional kind requiring C-u.
Alternatively, we could use switch-to-buffer-in-dedicated-window as
that user option: if the user sets it non-nil, we could take that as
an indication that they prefer the strongly-dedicated default.
WDYT?
next prev parent reply other threads:[~2023-08-20 6:13 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 15:38 bug#64619: [PATCH] Add toggle-window-dedicated command Spencer Baugh
2023-07-14 19:42 ` Philip Kaludercic
2023-07-14 21:17 ` Drew Adams
2023-07-14 23:58 ` sbaugh
2023-07-15 21:30 ` Drew Adams
2023-07-18 15:35 ` Spencer Baugh
2023-07-18 17:56 ` Philip Kaludercic
2023-07-15 5:44 ` Eli Zaretskii
2023-07-15 7:53 ` martin rudalics
2023-07-15 17:41 ` sbaugh
2023-07-15 18:16 ` martin rudalics
2023-07-18 15:34 ` Spencer Baugh
2023-08-19 13:34 ` sbaugh
2023-08-19 16:13 ` Philip Kaludercic
2023-08-19 16:20 ` sbaugh
2023-08-19 16:21 ` Philip Kaludercic
2023-08-19 20:02 ` sbaugh
2023-08-20 5:57 ` Eli Zaretskii
2023-08-21 13:00 ` sbaugh
2023-08-21 13:20 ` Gregory Heytings
2023-08-21 14:02 ` Eli Zaretskii
2023-08-21 19:22 ` Eli Zaretskii
2023-08-21 19:20 ` Eli Zaretskii
2023-10-13 1:33 ` sbaugh
2023-10-25 13:46 ` Eli Zaretskii
2023-08-19 16:43 ` Gregory Heytings
2023-08-19 20:06 ` sbaugh
2023-08-19 20:37 ` Gregory Heytings
2023-08-19 21:47 ` sbaugh
2023-08-19 22:36 ` Gregory Heytings
2023-08-20 6:13 ` Eli Zaretskii [this message]
2023-08-20 8:02 ` Gregory Heytings
2023-08-20 8:30 ` Eli Zaretskii
2023-08-20 8:41 ` Gregory Heytings
2023-08-20 8:54 ` Eli Zaretskii
2023-08-20 9:56 ` Gregory Heytings
2023-08-20 10:11 ` Eli Zaretskii
2023-08-20 10:25 ` Gregory Heytings
2023-08-20 14:09 ` sbaugh
2023-08-20 15:31 ` Eli Zaretskii
2023-08-20 21:56 ` Gregory Heytings
2023-08-21 11:23 ` sbaugh
2023-08-21 8:27 ` Augusto Stoffel
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=83edjyxmuz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64619@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=gregory@heytings.org \
--cc=philipk@posteo.net \
--cc=rudalics@gmx.at \
--cc=sbaugh@catern.com \
--cc=sbaugh@janestreet.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).