emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
* org-no-popups nilling display-buffer-alist
@ 2021-02-06  9:10 "Joshua O'Connor"
  2021-02-08  4:42 ` Kyle Meyer
  0 siblings, 1 reply; 2+ messages in thread
From: "Joshua O'Connor" @ 2021-02-06  9:10 UTC (permalink / raw)
  To: emacs-orgmode

Hi,
I wanted to control the positioning of the *Org Select* buffer, so I
first went to add a rule to 'display-buffer-alist'.
But I found it didn't work, as the function in question calls
'org-switch-to-buffer-other-window', which in turn calls an odd macro
'org-no-popups', which appears to let-nil the 'display-buffer-alist'.

I was wondering what the reason is for this? To me I expected this
variable to be reserved for me as a user to choose where windows can go,
which I think is a good plan given that you cannot possible know all the
configurations a user may want the window to appear.

As it stands, I resorted to redefining this function and removing the
'org-no-popups' section, but I have a sinking feeling that it's going to
end up with some odd window behaviour one day.

  (defun org-switch-to-buffer-other-window (args)
  ;;  (org-no-popups
  ;;     (apply 'switch-to-buffer-other-window args)))
    (switch-to-buffer-other-window args))

Thanks,

Joshua


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: org-no-popups nilling display-buffer-alist
  2021-02-06  9:10 org-no-popups nilling display-buffer-alist "Joshua O'Connor"
@ 2021-02-08  4:42 ` Kyle Meyer
  0 siblings, 0 replies; 2+ messages in thread
From: Kyle Meyer @ 2021-02-08  4:42 UTC (permalink / raw)
  To: Joshua O'Connor; +Cc: emacs-orgmode

\"Joshua O'Connor\" writes:

> Hi,
> I wanted to control the positioning of the *Org Select* buffer, so I
> first went to add a rule to 'display-buffer-alist'.
> But I found it didn't work, as the function in question calls
> 'org-switch-to-buffer-other-window', which in turn calls an odd macro
> 'org-no-popups', which appears to let-nil the 'display-buffer-alist'.
>
> I was wondering what the reason is for this? To me I expected this
> variable to be reserved for me as a user to choose where windows can go,
> which I think is a good plan given that you cannot possible know all the
> configurations a user may want the window to appear.

I agree that this should left to the user, and in 9.4 there was at least
some progress in making Org behave better in this department:
<https://orgmode.org/list/87eevw7jqk.fsf@gmail.com/>.

I've yet to do any extensive digging, but I suspect there wasn't a
strong reason for doing this.  I'd be in favor of a patch that drops the
use of display-buffer-alist.


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-02-08  4:43 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-02-06  9:10 org-no-popups nilling display-buffer-alist "Joshua O'Connor"
2021-02-08  4:42 ` Kyle Meyer

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