GNU bug report logs -
#64619
[PATCH] Add toggle-window-dedicated command
Previous Next
Reported by: Spencer Baugh <sbaugh <at> janestreet.com>
Date: Fri, 14 Jul 2023 15:40:02 UTC
Severity: wishlist
Tags: patch
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
> Date: Sun, 20 Aug 2023 09:56:06 +0000
> From: Gregory Heytings <gregory <at> heytings.org>
> cc: 64619 <at> debbugs.gnu.org, philipk <at> posteo.net, sbaugh <at> janestreet.com,
> sbaugh <at> catern.com, rudalics <at> gmx.at, drew.adams <at> oracle.com
>
> > A user who didn't customize switch-to-buffer-in-dedicated-window does
> > not necessarily want his/her dedicated windows to be strongly dedicated
> > by default. Which is why one of the alternatives I suggested is to use
> > the value of that variable as the indication which kind of dedication to
> > use by default.
>
> That wouldn't really work, alas. The mapping would be:
>
> switch-to-buffer-in-dedicated-window t => weakly dedicated
>
> switch-to-buffer-in-dedicated-window non-t => strongly dedicated
I meant the opposite mapping, actually.
> Weakly dedicating a window when switch-to-buffer-in-dedicated-window is t
> is not really useful. And the default value of
> switch-to-buffer-in-dedicated-window is nil, so the default would be
> strongly dedicated anyway.
There's an inherent problem with using
switch-to-buffer-in-dedicated-window for this purpose anyway: it
doesn't necessarily allow switch-to-buffer to change the buffer in
such a window, it might ask the user whether to switch, and the window
is no longer dedicated if the switch takes place.
So I don't think this variable can serve the user preference for
whether the window should be strongly or weekly dedicated by default.
This bug report was last modified 1 year and 260 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.