From: Max Nikulin <email@example.com> To: firstname.lastname@example.org Subject: Re: [PATCH] [BUG] Org 9.5: org-goto UI seems broken Date: Mon, 18 Oct 2021 23:53:43 +0700 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> On 18/10/2021 16:25, Eric S Fraga wrote: > On Sunday, 17 Oct 2021 at 23:35, Max Nikulin wrote: >> So >> >> (setq display-buffer-base-action >> '((display-buffer-reuse-window display-buffer-pop-up-frame) >> (reusable-frames . 0))) >> >> should not be considered as shooting a foot. > > I am not sure I understand what you are or are not proposing but org > should not be setting this variable. This variable is for the "user", > not the package, to set. I was trying to say that even with such *user* setup, behavior of Org should be reasonable. In particular, with draft patch I posted, *small* org-goto help buffer should not cause appearance of a new frame despite of `display-buffer-base-action' setting cited above, that is suitable for *regular* buffers. User still has opportunity to request arbitrary action for "*Org Help*" buffer through `display-buffer-alist'. > I actually think that org imposes too much of its own view on how > buffers should be managed & displayed. I am constantly annoyed (and > posted about this recently to the list with no response) that capture > buffers pop up all over the place and it doesn't seem like I have any > control at all. I agree that behavior of `org-add-note' is extremely intrusive. On the other hand I have no idea concerning its preferred behavior by default. I do not think that something like `org-src-window-setup' should be introduced for notes and captures. Ideally it should have reasonable behavior by default and should be adjustable through `display-buffer-alist'. Currently I can not suggest a snippet for `display-buffer-alist' to exclude zoom or teams windows from candidates for `switch-to-buffer-other-window' (that is called from `org-capture').
next prev parent reply other threads:[~2021-10-18 16:54 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-05 6:31 Adam Porter 2021-10-05 11:35 ` Max Nikulin 2021-10-05 12:45 ` [PATCH] " Ihor Radchenko 2021-10-05 12:52 ` Adam Porter 2021-10-05 14:49 ` Max Nikulin 2021-10-05 16:32 ` Ihor Radchenko 2021-10-07 16:14 ` Max Nikulin 2021-10-08 10:22 ` Marco Wahl 2021-10-12 14:59 ` Max Nikulin 2021-10-12 20:58 ` Marco Wahl 2021-10-13 1:35 ` Ihor Radchenko 2021-10-13 9:44 ` Marco Wahl 2021-10-13 12:23 ` Max Nikulin 2021-10-13 12:35 ` Eric S Fraga 2021-10-14 9:54 ` Marco Wahl 2021-10-14 10:16 ` Ihor Radchenko 2021-10-14 15:44 ` Max Nikulin 2021-10-15 16:37 ` Max Nikulin 2021-10-16 6:52 ` Ihor Radchenko 2021-10-17 16:35 ` Max Nikulin 2021-10-18 9:25 ` Eric S Fraga 2021-10-18 16:53 ` Max Nikulin [this message] 2021-10-19 7:45 ` Eric S Fraga 2021-10-05 12:48 ` Adam Porter
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 \ --email@example.com' \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH] [BUG] Org 9.5: org-goto UI seems broken' \ /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).