GNU bug report logs - #67249
30.0.50; `same-frame` equivalent for `display-buffer-alist`

Previous Next

Full log

View this message in rfc822 format

From: martin rudalics <rudalics <at> gmx.at>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 67249 <at> debbugs.gnu.org
Subject: bug#67249: 30.0.50; `same-frame` equivalent for `display-buffer-alist`
Date: Sat, 25 Nov 2023 10:00:20 +0100

>> Do you mean 'display-buffer-override-next-command' and
>> 'display-buffer-record-window'?
>
> I mostly noticed `display-buffer-other-frame` whose name (to me)
> suggests it can be used in an ACTION.  The two you cite could be
> considered as colliding, but since their name doesn't suggest they're
> going to "display a buffer", they didn't bother me.
>
> Hmm... after looking a bit more maybe it's not that bad, since the
> calling convention can be used to distinguish them
> (e.g. `display-buffer-other-frame` doesn't take an ALIST after the
> BUFFER).

'display-buffer-other-frame' was in files.el so C-x 5 C-o could be bound
to it - mainly as counterpart to C-x 4 C-o, I suppose.  It would be more
consistent to have two functions say 'show-buffer-other-window' and
'show-buffer-other-frame' we could bind to C-x 4 C-b and C-x 5 C-b and
assign them appropriate action functions but I'm not sure whether people
would like it.

martin

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.