Re: [O] '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/)]

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

Re: [O] '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/)]

Hello, Hassan Dar 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-fra

[O] '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/)]

Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org-mode mailing list. --

[O] org-switch-to-buffer-other-window

Hello, org-switch-to-buffer-other-window should probably dynamically bind display-buffer-function to nil, along with the other variables it does. I use display-buffer-function on my system to do some tricky stuff with frames, and I think org-switch-to-buffer-other-window would probably want to ove