From: Ihor Radchenko <yantar92@posteo.net>
To: Amol Vaidya <amolvaidya06@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org-Capture Window Behavior
Date: Sun, 22 Sep 2024 17:02:22 +0000 [thread overview]
Message-ID: <87ldzjpqox.fsf@localhost> (raw)
In-Reply-To: <CAHBJKyU-bDG2UkPm53tJ7-P4kW=YjyizbTSSqEGoOuroxCYBzg@mail.gmail.com>
Amol Vaidya <amolvaidya06@gmail.com> writes:
> 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.
I see.
I think that you misunderstood what `display-buffer-base-action' is for.
It is only used when the Emacs package that is displaying the buffer
does not specify how to display it (in other words, calling
`display-buffer' without specifying ACTION argument)
That's not what Org capture do. Org capture does tell Emacs how to
display the buffer. Only when the user explicitly overrides Org capture
display settings (via `display-buffer-alist' or
`display-buffer-overriding-action'), the default behavior is changed.
If you look into the docstring of `display-buffer', you will see that
there are a number of user settings with different priorities:
display-buffer builds a list of action functions and an action
alist by combining any action functions and alists specified by
display-buffer-overriding-action, display-buffer-alist, the
ACTION argument, display-buffer-base-action, and
display-buffer-fallback-action (in order). Then it calls each
function in the combined function list in turn, passing the
buffer as the first argument and the combined action alist as the
second argument, until one of the functions returns non-nil.
There is no bug in Org capture that we provide ACTION argument to hint
Emacs using what we believe is a better default compared to generic
buffer popups.
For you, as a user, the right way to configure how Org capture window is
displayed is customizing `display-buffer-alist'.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-09-22 17:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 0:31 Org-Capture Window Behavior Amol Vaidya
2024-09-16 19:24 ` Ihor Radchenko
2024-09-16 20:34 ` Amol Vaidya
2024-09-17 18:48 ` Ihor Radchenko
2024-09-17 21:28 ` Amol Vaidya
2024-09-22 8:22 ` Ihor Radchenko
2024-09-22 16:52 ` Amol Vaidya
2024-09-22 17:02 ` Ihor Radchenko [this message]
2024-09-22 17:33 ` Amol Vaidya
2024-09-22 17:47 ` Ihor Radchenko
2024-09-22 18:26 ` Amol Vaidya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ldzjpqox.fsf@localhost \
--to=yantar92@posteo.net \
--cc=amolvaidya06@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).