From: Samuel Wales <firstname.lastname@example.org> To: Jack Kamm <email@example.com> Cc: firstname.lastname@example.org Subject: Re: [RFC PATCH] Changes to pop-up source buffers Date: Sat, 18 Jan 2020 19:46:21 -0700 [thread overview] Message-ID: <CAJcAo8vt5+WVrNykbBnw3QQJe1dFAU2H_nf-+yzjKApsop-CBg@mail.gmail.com> (raw) In-Reply-To: <email@example.com> On 1/18/20, Jack Kamm <firstname.lastname@example.org> wrote: > What setting of org-src-window-setup are you using? If it is > "current-window" or "reorganize-frame", this patch shouldn't affect you > at all, as those implementations are left the same. you're right, i have that set to current-window, as you might expect. and it is reasonable to expect that any patch would continue to respect it. thanks for your response. jack> A final advantage I'd like to note for pop-to-buffer and quit-restore-window, is that these are the mechanisms used by many built-in Emacs functions to pop up and close windows, such as *Help* windows. i'm not sure what the latest is on what one should use. or whether the latest is on what one should use is problematic for my modest needs. maybe you have looked into the former. help does things like popping up in the fisrt place, opening a linked help buffer, and opening up source code. idk if they all use the same mechanism? i've had issues with 2-3 of them. anomalies on rare occasions occur despite my kludging. iirc stefan once wrote that using the wrong function will break his configuration. there are subtly different purposes for displaying a buffer. one covers the minibuffer, or something.
next prev parent reply other threads:[~2020-01-19 2:46 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-01-18 17:33 Jack Kamm 2020-01-18 18:56 ` Samuel Wales 2020-01-18 19:27 ` Jack Kamm 2020-01-19 2:46 ` Samuel Wales [this message] 2020-01-19 3:24 ` Kyle Meyer 2020-01-19 17:13 ` Jack Kamm 2020-01-21 4:10 ` Kyle Meyer 2020-01-22 5:06 ` Jack Kamm 2020-01-25 4:18 ` Kyle Meyer 2020-01-19 5:07 ` stardiviner
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=CAJcAo8vt5+WVrNykbBnw3QQJe1dFAU2H_nf-+yzjKApsop-CBg@mail.gmail.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [RFC PATCH] Changes to pop-up source buffers' \ /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).