From: Ihor Radchenko <yantar92@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: jan.seeger@thenybble.de, emacs-orgmode@gnu.org,
dal-blazej@onenetbeyond.org
Subject: Re: Bug: org-no-popups disregards display-buffer-fallback-action [9.4.6 (9.4.6-13-g4be129-elpaplus @ /home/jeeger/.emacs.d/elpa/org-plus-contrib-20210920/)]
Date: Sun, 14 Nov 2021 20:40:29 +0800 [thread overview]
Message-ID: <87a6i6hpvm.fsf@localhost> (raw)
In-Reply-To: <87bl2n0wb9.fsf@ucl.ac.uk>
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> On Sunday, 14 Nov 2021 at 14:08, Ihor Radchenko wrote:
>> Can you elaborate? We are looking forward for ideas how to improve Org
>> in this area. More concrete suggestions are welcome.
>
> I posted about this some weeks ago. It would be desirable to have org
> manage window placement much less, if at all. Emacs has sufficient
> customizations possible for window management, display-buffer-alist
> being the default variable to customize. I am constantly fighting org
> and find that it just does not allow me to configure window placement to
> my satisfaction, especially on *ultra-wide* monitors.
I thought that display-buffer-alist should be sufficient to control the
window placement in Org. Isn't it (on main)?
I recall you posted a message about "window management for logging and
capturing notes", but you can easily change the capture window location
with display-buffer-alist.
> My suggestion would be to remove all/most window management from org
> itself and simply suggest possible settings for display-buffer-alist,
> say.
We still need to have reasonable defaults. They can always be
overwritten by display-buffer-alist.
Best,
Ihor
next prev parent reply other threads:[~2021-11-14 12:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 7:50 Jan Seeger via General discussions about Org-mode.
2021-11-10 10:20 ` Ihor Radchenko
2021-11-13 17:34 ` dal-blazej
2021-11-14 6:08 ` Ihor Radchenko
2021-11-14 12:13 ` Eric S Fraga
2021-11-14 12:40 ` Ihor Radchenko [this message]
2021-11-14 19:37 ` Eric S Fraga
2021-11-14 23:03 ` dal-blazej
2021-11-15 9:57 ` Eric S Fraga
2021-11-15 16:54 ` org-capture windows Max Nikulin
2021-11-15 18:29 ` Eric S Fraga
2021-11-15 19:40 ` Bug: org-no-popups disregards display-buffer-fallback-action [9.4.6 (9.4.6-13-g4be129-elpaplus @ /home/jeeger/.emacs.d/elpa/org-plus-contrib-20210920/)] Daniel Kraus
2021-11-15 7:41 ` Jan Seeger via General discussions about Org-mode.
2021-11-13 13:15 ` Bug: org-no-popups disregards display-buffer-fallback-action 9.4.6 Max Nikulin
2021-11-15 7:42 ` Jan Seeger via General discussions about Org-mode.
2021-11-15 7:49 ` Jan Seeger via General discussions about Org-mode.
2021-11-17 14:49 ` Max Nikulin
2021-11-10 7:50 Bug: org-no-popups disregards display-buffer-fallback-action [9.4.6 (9.4.6-13-g4be129-elpaplus @ /home/jeeger/.emacs.d/elpa/org-plus-contrib-20210920/)] Jan Seeger via General discussions about Org-mode.
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=87a6i6hpvm.fsf@localhost \
--to=yantar92@gmail.com \
--cc=dal-blazej@onenetbeyond.org \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=jan.seeger@thenybble.de \
--subject='Re: Bug: org-no-popups disregards display-buffer-fallback-action [9.4.6 (9.4.6-13-g4be129-elpaplus @ /home/jeeger/.emacs.d/elpa/org-plus-contrib-20210920/)]' \
/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
Code repositories for project(s) associated with this 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).