emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: <h@hassandar.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: '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/)]
Date: Tue, 13 Oct 2015 23:19:01 +0100	[thread overview]
Message-ID: <561d8356.a795b40a.198db.7faf@mx.google.com> (raw)
In-Reply-To: <87zizmxzfa.fsf@nicolasgoaziou.fr>

[-- Attachment #1: Type: text/plain, Size: 1719 bytes --]

I worked around it by using an elisp ‘advice’ snippet another user suggested (http://emacs.stackexchange.com/questions/17112/prevent-org-todo-pop-up-window-from-displaying-in-new-frame-dedicated-window)

Before that I wasted several hours trying to ‘fix’ the problem in various ways. I imagine org is overriding default handling for a good reason, but it is frustrating to have to override said functionality with a code-snippet, which will undoubtedly break at some point while I scratch my head to understand how I can fix it!



From: Nicolas Goaziou
Sent: 13 October 2015 9:52 PM
To: Hassan Dar
Cc: emacs-orgmode@gnu.org
Subject: Re: '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/)]


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



[-- Attachment #2: Type: text/html, Size: 4393 bytes --]

      reply	other threads:[~2015-10-13 22:19 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
2015-10-13 22:19   ` h [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=561d8356.a795b40a.198db.7faf@mx.google.com \
    --to=h@hassandar.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).