From: Ihor Radchenko <yantar92@posteo.net>
To: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
Cc: Ship Mints <shipmints@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Add org-src-is-fontify-buffer-p (patch attached)
Date: Sat, 18 Jan 2025 12:48:48 +0000 [thread overview]
Message-ID: <87frlgqocv.fsf@localhost> (raw)
In-Reply-To: <735ddb50-9ad3-4603-b3ca-58b99bfba949@vodafonemail.de>
Jens Schmidt <jschmidt4gnu@vodafonemail.de> writes:
> Um, sorry for butting in, but I also have an interest of recognizing
> Org's special source environments, see here:
>
> https://list.orgmode.org/9eaf7099554d488d921e64c4b2852a0d@vodafonemail.de/
>
> That thread led to nowhere back then, but I think it still makes
> sense to have the various Org source environments detectable in
> a defined and explicit way, and Stephane's request reminded me
> about that.
AFAIR, your request was not about detecting "src edit" buffers, but about
detecting when a command is called in those buffers in very specific
scenario - by `org-babel-do-in-edit-buffer', while keeping the normal
behavior when editing those buffers interactively.
> While one could use buffer names also for detecting the source edit
> buffers ("*Org Src collateral.org[ shell ]*"), it feels somehow
> brittle, since names can change. So why not extend on Stephane's
> request and provide some variable that informs about the various
> types of Org source environments?
How would that help your original request?
> Like a variable named `org-src-environment-type' bound dynamically
> to possible values, e.g. `edit' or `fontify'?
I am reluctant. This will force us to make sure that we arrange this
variable appropriately in every single temporary buffer Org creates for
various purposes. In other words, it will increase maintenance burden.
Unless strongly justified, I am not going to do it.
--
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>
prev parent reply other threads:[~2025-01-18 12:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-18 0:39 Add org-src-is-fontify-buffer-p (patch attached) Ship Mints
2025-01-18 7:29 ` Ihor Radchenko
2025-01-18 9:27 ` Ship Mints
2025-01-18 11:20 ` Ihor Radchenko
2025-01-18 11:28 ` Ship Mints
2025-01-18 11:38 ` Ihor Radchenko
2025-01-18 11:54 ` Ship Mints
2025-01-18 11:57 ` Ship Mints
2025-01-18 12:42 ` Ihor Radchenko
2025-01-18 12:53 ` Ship Mints
2025-01-18 12:59 ` Ihor Radchenko
2025-01-18 12:15 ` Jens Schmidt
2025-01-18 12:33 ` Ship Mints
2025-01-18 12:48 ` Ihor Radchenko [this message]
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=87frlgqocv.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=jschmidt4gnu@vodafonemail.de \
--cc=shipmints@gmail.com \
/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).