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 19:42:28 +0100]:
>
>> and, since you want to use `display-buffer-reuse-or-same-window' in
>> `shell'-like functions, I will not be able to avoid that.
>
> 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?!
How?

>> I would much prefer that we use `pop-to-buffer' or `display-buffer'
>> everywhere (deprecating all those `pop-to-buffer-*' functions)
>
> I might agree.  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.


> The greatest problem the 'display-buffer-alist' functionality had to
> deal with was to leave the default behavior unchanged while adding
> enough facilities so users could change the behavior to their like.

IIUC, using `pop-to-buffer' for *shell* and adding something like

(("*shell*" (display-buffer-reuse-window)))

to `display-buffer-alist' is equivalent to using
`pop-to-buffer-same-window' on *shell*.

>> and let the _users_ decide how to display _all_ buffers using the standard
>> `display-buffer-alist' functionality.
>
> Deciding is not sufficient.  Users have to customize it and you should
> have now noticed by yourself that dealing with 'display-buffer-alist' is
> not entirely trivial.

Understatement of the year.

This is why I want us to use it instead of `pop-to-buffer-*' - to give
users a good starting example to modify.

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.2022
http://childpsy.net http://calmchildstories.com http://steingoldpsychology.com
https://mideasttruth.com https://jihadwatch.org
Your mouse has moved - WinNT has to be restarted for this to take effect.