From: "Christopher M. Miles" <numbchild@gmail.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: Org Babel related popup buffer names not unified
Date: Sat, 13 Jul 2024 18:19:41 +0800 [thread overview]
Message-ID: <669254cb.170a0220.70dba.1926@mx.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
I use bellowing config to manage Org Babel related popup buffer displaying.
(add-to-list 'display-buffer-alist '("^\\*Org Src.*\\*" . (display-buffer-below-selected)))
(add-to-list 'display-buffer-alist '("^\\*Org Babel Results\\*" . (display-buffer-below-selected)))
(add-to-list 'display-buffer-alist '("^\\*Org Babel Preview.*\\*" . (display-buffer-below-selected)))
(add-to-list 'display-buffer-alist '("^\\*Org Babel Error Output\\*" . (display-buffer-below-selected)))
I found in org-mode source code, some places use "*Org-Babel Results*",
somewhere does not have dash between *Org-Babel, "*Org-Babel Results*".
Other Org Babel related buffer names has same situations.
I hope org-mode can unify those buffer names.
Ihor, WDYT?
--
[ stardiviner ]
I try to make every word tell the meaning that I want to express without misunderstanding.
Blog: https://stardiviner.github.io/
IRC(libera.chat, freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next reply other threads:[~2024-07-13 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 10:19 Christopher M. Miles [this message]
2024-07-13 13:38 ` Org Babel related popup buffer names not unified Ihor Radchenko
[not found] ` <66936038.050a0220.dc39.4457@mx.google.com>
[not found] ` <87plrgjmy6.fsf@localhost>
[not found] ` <6693b7b0.170a0220.c3ff1.47dc@mx.google.com>
[not found] ` <87msmkjifd.fsf@localhost>
[not found] ` <66948e56.170a0220.581d4.07f6@mx.google.com>
[not found] ` <8734oak95j.fsf@localhost>
[not found] ` <6695bb90.170a0220.bf95b.f400@mx.google.com>
2024-07-16 17:14 ` [PATCH v3] " Ihor Radchenko
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=669254cb.170a0220.70dba.1926@mx.google.com \
--to=numbchild@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).