Re: Add org-src-is-fontify-buffer-p (patch attached)

[Ship Mints]

Yes, could do, and nothing needed by org-mode or markdown-mode. Could also test for buffer-file-name nil. Or test both. Let's recommend that simpler approach and I will rescind my markdown PR in favor of this simpler suggestion.

On Sat, Jan 18, 2025 at 6:18 AM Ihor Radchenko <yantar92@posteo.net> wrote:

Ship Mints <shipmints@gmail.com> writes:

> Eglot was the first request cited. For python programmers that rely on per
> project/directory-local or per-buffer virtual environment set up, this can
> be heavier than needed just for fontification. I enable eglot manually, but
> I do use python virtual environments and would disable initialization in
> fontification buffers.

Ok. Fair enough.

> I'd prefer a more generic interface than propagating org internals like the
> format of the fortification buffer name. It's what I submitted to the
> markdown repo also. The buffer name scheme can change in the future without
> impacting this feature.

>From my point of view, the interface you suggest is not generic enough.
It only addresses a single use case - Org fontification.

What about another, more general approach - check if buffer name starts
with space? By convention, buffers with names starting with space are
considered internal.

--
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>