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 08:22:04 +0000 [thread overview]
Message-ID: <875xqortcj.fsf@localhost> (raw)
In-Reply-To: <CAHBJKyWWQLVpFzDXZnKoxNKN=qtg5tS4D6S=Za=7j4TDUnBGig@mail.gmail.com>
Amol Vaidya <amolvaidya06@gmail.com> writes:
> (Apologies for replying to this twice Ihor, forgot to reply-all last time.)
>
> The linked video was from an emacs -q, so I have made no modifications to
> display-buffer-alist, and my understanding is that emacs -q is equivalent
> to an empty init file. If that's not correct, I'm not sure what kind of
> reproducer I need to be providing.
Yes, you are correct. emacs -q is an equivalent to the empty init file.
And what you get with emacs -q is also expected - the default window placement.
There is no bug in what you have shown - Org mode uses its defaults (we
need to have some).
> I am using Emacs 29.4. I am using org 9.7.11. I don't know what the
> protocol for submitting long code excerpts is to this mailing list, so I
> apologize if this is not the preferred method, but the output of
> org-submit-bug-report is given below. If there is other information I
> should provide, please let me know.
I am trying to figure out your report that Org mode does not respect
`display-buffer-alist'. Org mode, since Org 9.7, should respect user
customization in `display-buffer-alist'.
What I want from you is sufficient information for me to replicate the
problem you are seeing on my computer. Without such information, I
simply cannot diagnose the problem.
The usual way to produce such information is providing detailed steps,
starting from emacs -Q, that demonstrate the problem.
In your case, it is probably something like
1. emacs -Q
2. Evaluate (setq display-buffer-alist ...)
3. Run M-x org-capture ...
4. Observe display-buffer-alist not being respected
See also https://orgmode.org/manual/Feedback.html
May you please provide such information for me?
--
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 8:21 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 [this message]
2024-09-22 16:52 ` Amol Vaidya
2024-09-22 17:02 ` Ihor Radchenko
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=875xqortcj.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).