From: Ship Mints <shipmints@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Add org-src-is-fontify-buffer-p (patch attached)
Date: Sat, 18 Jan 2025 07:53:06 -0500 [thread overview]
Message-ID: <CAN+1Hbo8kc4oLyA0g-CzcqNE5JRXT_9Yg5N8x2EZzi7L4KHCeA@mail.gmail.com> (raw)
In-Reply-To: <87jzasqony.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
Makes sense. I'm not set up to contribute to WORG, perhaps you can do it,
if you don't mind?
On Sat, Jan 18, 2025 at 7:39 AM Ihor Radchenko <yantar92@posteo.net> wrote:
> Ship Mints <shipmints@gmail.com> writes:
>
> > This could be added to the org-mode documentation as a hint for those who
> > use native fontification. Should I send a patch for that or trivial
> enough
> > you'd do it, if you agree?
>
> I am not sure if this problem is so common that we need to put it into
> the manual.
>
> I think creating a WORG page that collects performance hacks and
> suggestions could be a good alternative.
>
> --
> 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>
>
[-- Attachment #2: Type: text/html, Size: 1592 bytes --]
next prev parent reply other threads:[~2025-01-18 12:55 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 [this message]
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
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=CAN+1Hbo8kc4oLyA0g-CzcqNE5JRXT_9Yg5N8x2EZzi7L4KHCeA@mail.gmail.com \
--to=shipmints@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).