emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: JV <misc@jeffvalk.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-agenda-tree-to-indirect-buffer does not respect org-indirect-buffer-display value
Date: Sat, 11 May 2024 13:26:53 +0000	[thread overview]
Message-ID: <878r0gv5r6.fsf@localhost> (raw)
In-Reply-To: <1a4c7a04-8536-40c7-899e-ba433a1252fd@jeffvalk.com>

JV <misc@jeffvalk.com> writes:

> `org-agenda-tree-to-indirect-buffer' does not respect the
> `org-indirect-buffer-display' value of 'current-window unless invoked 
> with a prefix arg.
> The function does respect all other values for
> `org-indirect-buffer-display'. And it does respect the value
> 'current-window when the function is called with a prefix arg.
> However, without prefix arg, 'current-window and 'other-window are 
> treated the same and call to `split-window' is made.

Thanks for reporting!
Fixed, on main.

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>

      reply	other threads:[~2024-05-11 13:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-09 17:40 [BUG] org-agenda-tree-to-indirect-buffer does not respect org-indirect-buffer-display value JV
2024-05-11 13:26 ` Ihor Radchenko [this message]

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:

  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=878r0gv5r6.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=misc@jeffvalk.com \


* 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


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).