Julian Flake <[email protected]> writes: > It seems that org-agenda-goto changed "recently" > (15226075169a6a0fbcc801863637dc6d24ea6bc8) and I have a usability > / customzability issue in combination with my frames-only-mode-ish > workflow, now. (I'm only 99% sure that frames-only-mode handled > the following situation better before the commit). > > If I hit TAB in my org-agenda, I want to go to the entry at point > and open the corresponding org file in a new frame instead of a > new window. > > There are different ways to work around this, e.g. by customizing > display-buffer-alist or by an advice to use tear-off-window after > org-agenda-goto and more (thanks to bpalmer and bata in > IRC). Maybe there is a simple fix in org-agenda-goto itself?
Users are supposed to customize the popup behavior via display-buffer-alist. In the past, it worked (AFAIU) because frames-only-mode sets pop-up-frames that happened to work with the old code. But pop-up-frames is finicky and only works when default action is not specified. > org-agenda-goto passes (display-buffer-reuse-window > display-buffer-pop-up-window) to display-buffer. Maybe there is a > way to customize this, I'd probably like to pass > (display-buffer-reuse-window display-buffer-pop-up-frame) instead. display-buffer-alist should be the way. Another way, of course, is an advice let-binding display-buffer-overriding-action. I do not think that there is a bug here. We switched to using display-buffer + ACTION setup because older behavior was limiting users in other ways (display-buffer-alist was not fully obeyed). Canceled. If you really can't find a way to customize the display, we might consider adding a user option or maybe asking Emacs upstream to provide user tooling for similar situations. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
