From: Eli Zaretskii <eliz@gnu.org>
To: sbaugh@catern.com
Cc: 64619@debbugs.gnu.org, philipk@posteo.net, sbaugh@janestreet.com,
rudalics@gmx.at, gregory@heytings.org, drew.adams@oracle.com
Subject: bug#64619: [PATCH] Add toggle-window-dedicated command
Date: Sun, 20 Aug 2023 18:31:44 +0300 [thread overview]
Message-ID: <83il99wx0f.fsf@gnu.org> (raw)
In-Reply-To: <87fs4dpzz5.fsf@catern.com> (sbaugh@catern.com)
> From: sbaugh@catern.com
> Date: Sun, 20 Aug 2023 14:09:35 +0000 (UTC)
> Cc: Eli Zaretskii <eliz@gnu.org>, 64619@debbugs.gnu.org, philipk@posteo.net,
> sbaugh@janestreet.com, rudalics@gmx.at, drew.adams@oracle.com
>
> Completely separate suggestion and possible resolution: Maybe we can
> have two commands, one which does weak dedication and the other strong
> dedication?
That'd be overkill, IMO. The single command is already borderline
(since dedicated windows were not introduced as an interactive
feature, but rather as a means for Lisp programs to control
display-buffer's otherwise "wild West" type behavior). Having two
commands is completely overboard. Let's not take this ad absurdum.
(Of course, you can always have a special command in your local init
file, if you need them both. Here we are talking about what the
majority of Emacs users will need.)
next prev parent reply other threads:[~2023-08-20 15:31 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
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 [this message]
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=83il99wx0f.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).