From: Jean Louis <bugs@gnu.support>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-agenda-list opens new frame with org-agenda-window-setup other-window and split-window-vertically [9.6 (release_9.6-49-g47d129 @ /home/data1/protected/Programming/Software/emacs/lisp/org/)]
Date: Sat, 24 Dec 2022 15:50:53 +0300 [thread overview]
Message-ID: <Y6b1rdAkK+Oxbuhc@protected.localdomain> (raw)
In-Reply-To: <to6mb3$apn$1@ciao.gmane.io>
* Max Nikulin <manikulin@gmail.com> [2022-12-24 14:06]:
> On 24/12/2022 14:52, Jean Louis wrote:
> > When I set following:
> > (setq org-agenda-window-setup 'other-window) with intention to get
> > agenda in other window, together with following:
> >
> > (setq split-window-preferred-function 'split-window-vertically)
> >
> > then
> >
> > (org-agenda-list)
> >
> > is not going to show itself in other window but in new or other frame.
>
> Is half of window width enough to display agenda? I do not see anything
> related to `split-window-preferred-function' and `split-window-vertically'
> in org, so it might be emacs specifics. However it might be indirect result
> of the `org-no-popups' hack.
Then it is probably not Org related, though affects also Org. P
lease close it as bug in Org.
I have reported is main Emacs bug as it does not behave logically, it
behaves as other-frame not as other-window
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
prev parent reply other threads:[~2022-12-24 12:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-24 7:52 [BUG] org-agenda-list opens new frame with org-agenda-window-setup other-window and split-window-vertically [9.6 (release_9.6-49-g47d129 @ /home/data1/protected/Programming/Software/emacs/lisp/org/)] Jean Louis
2022-12-24 11:04 ` Max Nikulin
2022-12-24 12:50 ` Jean Louis [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:
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=Y6b1rdAkK+Oxbuhc@protected.localdomain \
--to=bugs@gnu.support \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
/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).