[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: master 18b680cfd1: Fix bug#52467 by adding a new custom variable 'di
From: |
Juri Linkov |
Subject: |
Re: master 18b680cfd1: Fix bug#52467 by adding a new custom variable 'display-comint-buffer-action' |
Date: |
Tue, 11 Jan 2022 20:15:24 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (x86_64-pc-linux-gnu) |
>>> 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 latter, that already can be used. Only one convenience change
could be added to allow symbols in conditions:
(add-to-list 'display-buffer-alist
'((*comint* display-buffer-reuse-or-same-window (nil))))
> 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*))))
Maybe then allow a list: ((label . '(*shell* *comint*)))
- Re: master 18b680cfd1: Fix bug#52467 by adding a new custom variable 'display-comint-buffer-action', (continued)
- Re: master 18b680cfd1: Fix bug#52467 by adding a new custom variable 'display-comint-buffer-action', Juri Linkov, 2022/01/03
- Re: master 18b680cfd1: Fix bug#52467 by adding a new custom variable 'display-comint-buffer-action', martin rudalics, 2022/01/04
- Re: master 18b680cfd1: Fix bug#52467 by adding a new custom variable 'display-comint-buffer-action', martin rudalics, 2022/01/06
- Re: master 18b680cfd1: Fix bug#52467 by adding a new custom variable 'display-comint-buffer-action', Juri Linkov, 2022/01/06
- Re: master 18b680cfd1: Fix bug#52467 by adding a new custom variable 'display-comint-buffer-action', martin rudalics, 2022/01/07
- Re: master 18b680cfd1: Fix bug#52467 by adding a new custom variable 'display-comint-buffer-action', Sam Steingold, 2022/01/07
- Re: master 18b680cfd1: Fix bug#52467 by adding a new custom variable 'display-comint-buffer-action', Eli Zaretskii, 2022/01/07
- Re: master 18b680cfd1: Fix bug#52467 by adding a new custom variable 'display-comint-buffer-action', Sam Steingold, 2022/01/07
- Re: master 18b680cfd1: Fix bug#52467 by adding a new custom variable 'display-comint-buffer-action', Juri Linkov, 2022/01/11
- Re: master 18b680cfd1: Fix bug#52467 by adding a new custom variable 'display-comint-buffer-action', martin rudalics, 2022/01/11
- Re: master 18b680cfd1: Fix bug#52467 by adding a new custom variable 'display-comint-buffer-action',
Juri Linkov <=
- Re: master 18b680cfd1: Fix bug#52467 by adding a new custom variable 'display-comint-buffer-action', martin rudalics, 2022/01/12
- Re: master 18b680cfd1: Fix bug#52467 by adding a new custom variable 'display-comint-buffer-action', Juri Linkov, 2022/01/03
Re: master 18b680cfd1: Fix bug#52467 by adding a new custom variable 'display-comint-buffer-action', Sam Steingold, 2022/01/03