From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: org-no-popups disregards display-buffer-fallback-action 9.4.6
Date: Wed, 17 Nov 2021 21:49:53 +0700 [thread overview]
Message-ID: <sn34qj$t2p$1@ciao.gmane.io> (raw)
In-Reply-To: <893749f7-a709-674f-fe89-03574523396f@thenybble.de>
On 15/11/2021 14:49, Jan Seeger wrote:
> On 13.11.21 14:15, Max Nikulin wrote:
>
> My thought is that I have a perfectly good window manager that allows me
> to manage Emacs frames.
> ... Thus, I prefer to have my
> window manager manage Emacs frames, instead of adding yet another way to
> switch between multiple things being displayed at the same time, which I
> would have to do using Emacs windows.
>
> My current configuration is as follows:
>
> (setq display-buffer-base-action '((display-buffer-reuse-window display-buffer-pop-up-frame)
> (reusable-frames . 0)))
> (setq display-buffer-alist
> `(("\\*Packages\\*" display-buffer-pop-up-frame)
> ("\\*stdin.*\\*" display-buffer-same-window)
> ("\\*Help\\*" display-buffer-pop-up-frame)
> ("\\*.*\\*" display-buffer-pop-up-window)))
Thank you for sharing this. I have tried such setup. Behavior of Org
windows is terrible. "Standard" Emacs windows may be a bit strange
sometimes, but it is not really annoying.
If there is a *Help* buffer on the screen, another one is created if
help is called from some other buffer. Content of help frames is
synchronized. I suppose, second help frame on the same screen may be
avoided by adjusting configuration. (Side note: sometimes I do not mind
to have several help buffers showing different content, so I do not like
current limitation of help facilities.)
Frame may be split into halves by e.g. debugger window, C-h e, etc. It
does not matter whether it is full-screen or half-screen frame (OK, in
first case it split by vertical line, in second one by horizontal). Next
similar buffer is opened in new frame. I would expect that either always
new frame is created or decision depends on window size, not on number
of windows (1 or 2) in the frame.
I have tried your suggestion
> (defmacro org-no-popups (&rest body)
> "Suppress popup windows and evaluate BODY."
> `(let ((display-buffer-overriding-action '(display-buffer-pop-up-window)))
> ,@body))
It requires more work. C-c C-j org-goto is obviously broken with your
config due to recent changes. It fixes only first step of org-capture
(template selection) is fixed, window with buffer for capture is created
in the current frame, but new clone of frame is created.
I am still in doubts whether `display-buffer-overriding-action' or
ACTION argument of `display-buffer' should be used.
Actually I think that even org-capture should have two different
options: with new frame or withing existing frame. Maybe I will explain
it in detail in other part of this thread is response to Eric's message.
prev parent reply other threads:[~2021-11-17 14:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
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.
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
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 [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='sn34qj$t2p$1@ciao.gmane.io' \
--to=manikulin@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).