From: Timothy <tecosaur@gmail.com>
To: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] Fontification for inline src blocks
Date: Wed, 28 Apr 2021 15:14:13 +0800 [thread overview]
Message-ID: <87pmye51a3.fsf@gmail.com> (raw)
In-Reply-To: <87pmzf4bd0.fsf@gmail.com>
Timothy <tecosaur@gmail.com> writes:
> Hi All,
>
> I've been using inline src blocks a fair bit more recently, and I've
> thought it's a pity how bad they look as they are currently without
> fontification. A little digging into Org internals and font-lock later
> and we have this patch. I could speak about what's been done, but I
> think a screenshot does a much better comparison.
>
> For more details, see the attached patch.
Since this affects font-lock, display performance is obviously a key
concern, and so I have two things to note on that front:
1. I have been using this patch for over a month at this point,
frequently in a ~10k line Org file (my Emacs config), and there has
been no noticeable performance degradation
2. The most expensive part of this is the native syntax highlighting,
which is only used when `org-src-fontify-natively' is t, and the
second most expensive part (results formatting) is only performed
when `org-inline-src-prettify-results' (a new variable) is t.
In brief: I don't anticipate any significant performance implications of
this patch, though of course second opinions would be great :)
--
Timothy
next prev parent reply other threads:[~2021-04-28 7:14 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 15:00 [PATCH] Fontification for inline src blocks Timothy
2021-04-28 7:14 ` Timothy [this message]
2021-05-02 20:17 ` Timothy
2021-05-02 20:57 ` Tom Gillespie
2021-05-02 21:03 ` Timothy
2021-05-02 21:13 ` Tom Gillespie
2021-05-02 23:54 ` Tom Gillespie
2021-05-03 3:29 ` Timothy
2021-05-12 11:15 ` Timothy
2021-05-12 14:24 ` Ihor Radchenko
2021-05-12 14:47 ` Timothy
2021-05-12 15:53 ` Ihor Radchenko
2021-05-12 16:39 ` Timothy
2021-05-13 2:38 ` Tim Cross
2021-05-13 5:31 ` Ihor Radchenko
2021-05-18 12:06 ` Sébastien Miquel
2021-05-18 13:34 ` Timothy
2021-05-18 14:36 ` Sébastien Miquel
2021-04-29 22:59 ` TRS-80
2021-10-03 7:14 ` Ihor Radchenko
2021-10-03 7:16 ` Timothy
2021-10-03 9:09 ` Ihor Radchenko
2021-10-03 9:22 ` Timothy
2021-10-04 20:02 ` Protesilaos Stavrou
2021-11-21 14:09 ` Timothy
2021-11-22 11:52 ` Timothy
2021-11-22 12:23 ` Ihor Radchenko
2021-11-22 13:43 ` Timothy
2021-11-22 14:35 ` Ihor Radchenko
2021-11-22 14:37 ` Timothy
2021-11-23 13:30 ` Ihor Radchenko
2021-11-29 19:21 ` Timothy
2021-11-30 11:44 ` Timothy
2021-11-30 12:45 ` Sébastien Miquel
2021-11-30 12:46 ` Timothy
2021-11-30 12:21 ` Ihor Radchenko
2021-12-02 12:53 ` Eric S Fraga
2021-12-02 13:57 ` Faces for inline src blocks (was: [PATCH] Fontification for inline src blocks) Timothy
2021-12-02 15:52 ` Faces for inline src blocks Eric S Fraga
2021-12-02 15:56 ` Timothy
2021-12-02 16:15 ` Eric S Fraga
2021-11-23 10:45 ` [PATCH] Fontification " Vitaly Ankh
2021-11-23 13:45 ` Vitaly Ankh
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmye51a3.fsf@gmail.com \
--to=tecosaur@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.