Hello,
Again, I apologize for sending this email to you twice Ihor. I keep forgetting to hit reply-all. Anyway...
Thank you for your clarification. Just a minor point: my concern is that org-capture is not adhering to general display-buffer settings rather than specifically display-buffer-alist. In my case display-buffer-alist is nil when I run emacs -q, but according to section 29.13.1 of the Elisp manual, if display-buffer-alist is nil, then display-buffer should consult the display-buffer-base-action user option to decide where to display a buffer.
In my setup, when I run emacs -q display-buffer-base-action has the following value
((display-buffer--maybe-same-window
display-buffer-reuse-window
display-buffer--maybe-pop-up-frame-or-window
display-buffer-in-previous-window
display-buffer-use-some-window
display-buffer-pop-up-frame)).
So the steps to reproduce the behavior I'm encountering are as follows
1. Run emacs -q
2. C-x 3 C-x 3 to split the frame into three windows.
3. M-x org-capture [RET] t
At this point, only two windows are displayed, rather than the three that were originally open. I'm not entirely familiar with what all the display-functions in display-buffer-base-action do, but I don't believe any of them should result in windows being deleted. This suggests that org-capture may not be respecting that setting.
I also tried doing the following two alternative sets of steps, both leading to the same behavior
TEST 1:
1. Run emacs -q
2. M-x ielm
3. In ielm, run (setq display-buffer-base-action '((display-buffer-same-window)))
4. C-x 3 C-x 3 to split the frame into three windows
5. M-x org-capture [RET] t
------------------------------------------------------------------------------------------------------------
TEST 2:
1. Run emacs -q
2. M-x ielm
3. In ielm, run (add-to-list 'display-buffer-alist '("\\*CAPTURE*" (display-buffer-same-window)))
4. C-x 3 C-x 3 to split the frame into three windows
5. M-x org-capture [RET] t
In both cases, after running org-capture
, all other windows are deleted except one, regardless of the settings in display-buffer-base-action
or display-buffer-alist
. This leads me to believe that org-capture
may not be respecting those settings, particularly if delete-other-windows
is being called, as appears to be the case in org-capture-place-template
.
Please let me know if I can provide any additional details or further clarification.
Best regards,
Amol Vaidya