From: "\"Joshua O'Connor\"" <email@example.com> To: firstname.lastname@example.org Subject: org-no-popups overriding display-buffer-alist Date: Sat, 06 Feb 2021 16:33:25 +0000 [thread overview] Message-ID: <email@example.com> (raw) Hi, I was wondering what the reason is for Org to employ the tactic of overriding the variable 'display-buffer-alist' in a few places, using the 'org-no-popups' macro? It's my understanding that this variable is to be exclusively set by users, and acts as the "it's my program, I'll put windows where I want them" setting. The manual has this to say "display-buffer-alist and display-buffer-base-action are user options—Lisp programs must never set or rebind them. display-buffer-overriding-action, on the other hand, is reserved for applications—who seldom use that option and if they use it, then with utmost care." I've ended up with this rather inelegant cludge: (defun org-switch-to-buffer-other-window (args) "Switch to buffer in a second window on the current frame. In particular, do not allow pop-up frames. Returns the newly created buffer. Redefined to allow pop-up windows." ;; (org-no-popups ;; (apply 'switch-to-buffer-other-window args))) (switch-to-buffer-other-window args)) Does anyone know of a better way to reassert my window preferences? If concrete context will help: I'm specifically wanting to shift the "*Org Select*" buffers into a side window rather than them do whatever they want. Cheers, Joshua
next reply other threads:[~2021-02-06 16:34 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-06 16:33 "Joshua O'Connor" [this message] 2021-09-29 12:52 ` Ihor Radchenko
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: org-no-popups overriding display-buffer-alist' \ /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).