emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Hassan Dar <h@hassandar.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: 'org-switch-to-buffer-other-window' prevents customisation of pop-up buffers by binding key variables [8.2.10 (release_8.2.10 @ c:/Program Files/emacs/share/emacs/24.5/lisp/org/)]
Date: Tue, 13 Oct 2015 22:54:01 +0200	[thread overview]
Message-ID: <87zizmxzfa.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAMOggMt0DUcX9xaXAJtg4Lgs4b96ez-UeD=pXoHh3hGxCdeWmg@mail.gmail.com> (Hassan Dar's message of "Sun, 4 Oct 2015 10:29:44 +0100")

Hello,

Hassan Dar <h@hassandar.com> writes:

> As seen in the following StackExchange questions:
>
> http://emacs.stackexchange.com/questions/14817/how-to-control-where-the-org-todo-keywords-buffer-displays
>
> http://emacs.stackexchange.com/questions/17112/prevent-org-todo-pop-up-window-from-displaying-in-new-frame-dedicated-window
>
> The org-no-popups macro (which is leveraged by '
> org-switch-to-buffer-other-window' let-binds key variables such as
> "display-buffer-alist" to 'nil'.
>
> This ultimately prevents a user from
> customising pop-ups generated by org in the same way they would with
> other pop-up windows.

I'm not a big fan of Org's opinionated way to handle windows either.
However, couldn't you use `display-buffer-overriding-action' in this
case? It is checked before `display-buffer-alist'.

Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2015-10-13 20:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-04  9:29 'org-switch-to-buffer-other-window' prevents customisation of pop-up buffers by binding key variables [8.2.10 (release_8.2.10 @ c:/Program Files/emacs/share/emacs/24.5/lisp/org/)] Hassan Dar
2015-10-13 20:54 ` Nicolas Goaziou [this message]
2015-10-13 22:19   ` 'org-switch-to-buffer-other-window' prevents customisation ofpop-up buffers by binding key variables [8.2.10 (release_8.2.10 @ c:/ProgramFiles/emacs/share/emacs/24.5/lisp/org/)] h

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=87zizmxzfa.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=h@hassandar.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

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