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

[martin rudalics]

>> Note that a 'pop-to-buffer' call can add an arbitrary element like a
>> label to the action alist and 'display-buffer-alist' can, via a
>> function, interpret that label in any which way.  So we do not have to
>> add anything new to make such things work.  The important aspects are
>> rather discoverability and ease of documentation.
>
> Indeed, this would be nice to have:
>
>    (pop-to-buffer "*shell*" '(display-buffer-reuse-or-same-window .
>                               ((label . *shell*))))

The question is who we think should take care of this:
'display-buffer-assq-regexp' in association with 'display-buffer-alist'?
Or just a function specified via 'display-buffer-alist'?  The latter can
be already done now with some documentation support maybe.  The former
also requires a few code changes and a decision how to handle

(pop-to-buffer "*shell*" '(display-buffer-reuse-or-same-window
                           . ((label . *shell*) (label . *comint*))))

martin