Re: master 18b680cfd1: Fix bug#52467 by adding a new custom variable 'display-comint-buffer-action'

[Sam Steingold <sds@gnu.org>]

> * martin rudalics <ehqnyvpf@tzk.ng> [2021-12-31 20:40:20 +0100]:
>
>>> That's an exaggeration.  You can always work around this problem via
>>> 'display-buffer-alist'.
>>
>> Are you saying that by manipulating `display-buffer-alist' I can stop
>> `pop-to-buffer' from using the same window?!
>
> Yes.

Of course.

I meant `pop-to-buffer-same-window', not `pop-to-buffer'.

Sorry.

>> How?
>
> (add-to-list 'display-buffer-alist
>              '("\\*shell\\*" nil (inhibit-same-window . t)))
>
> (pop-to-buffer-same-window "*shell*")

Huh, apparently, you have mastered ESP ;-)

> Have you ever read sections 29.15.5 and 29.15.6 of the Elisp manual?

Presumably you mean "29.13.5 Precedence of Action Functions" and
"29.13.6 The Zen of Buffer Display".
I think I did, long ago, and I will re-read them now.

> These contain numerous examples of how to add the 'inhibit-same-window'
> action alist entry to do precisely that.
>
>>> But we cannot simply convert everything that used
>>> 'switch-to-buffer' once (or still uses it) to use 'pop-to-buffer'
>>> instead.
>>
>> That's okay, we can leave `switch-to-buffer' alone.
>
> Then we have to leave 'pop-to-buffer-same-window' alone too.
> 'pop-to-buffer-same-window' is the customizable version of
> 'switch-to-buffer'.

I did not realize that, thank you for pointing this out.


-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.2022
http://childpsy.net http://calmchildstories.com http://steingoldpsychology.com
https://jihadwatch.org https://ij.org/ https://ffii.org http://think-israel.org
You won't get smarter by calling me a fool.