From: "Christopher M. Miles" <numbchild@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: numbchild@gmail.com, Org Mode <emacs-orgmode@gnu.org>
Subject: [DONE] Re: [SOMEDAY] Re: [BUG] inline src_lang code is not fontified on headline
Date: Sat, 13 Aug 2022 21:43:59 +0800 [thread overview]
Message-ID: <m2edxkb6mq.fsf@numbchild@gmail.com> (raw)
In-Reply-To: <m2tu7vxbui.fsf@numbchild>
[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]
Confirmed problem fixed.
"Christopher M. Miles" <numbchild@gmail.com> writes:
> [[PGP Signed Part:Undecided]]
>
> Ihor Radchenko <yantar92@gmail.com> writes:
>
>> "Christopher M. Miles" <numbchild@gmail.com> writes:
>>
>>> The src_lang code fontification is normal in content, but not correctly
>>> fontified on headline.
>>>
>>> There is a screenshot in attachment.
>>
>> Thanks for reporting!
>> Note that a major rewrite of Org fontification is WIP.
>> See https://orgmode.org/list/87ee7c9quk.fsf@localhost
>>
>> AFAIU, your example should work correctly with the new fontification.
>> You can check yourself using the WIP feature/org-font-lock-element
>> branch from https://github.com/yantar92/org
>>
>> Best,
>> Ihor
>
> Thanks for answer, I checked out the feature/org-font-lock-element
> branch on GitHub repo, and wait for it be fixed.
--
[ 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 --]
prev parent reply other threads:[~2022-08-13 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <62c170f6.1c69fb81.59d94.214bSMTPIN_ADDED_BROKEN@mx.google.com>
2022-07-03 11:25 ` [BUG] inline src_lang code is not fontified on headline Ihor Radchenko
2022-07-06 1:34 ` [SOMEDAY] " Christopher M. Miles
[not found] ` <m2tu7vxbui.fsf@numbchild>
2022-08-13 13:43 ` Christopher M. Miles [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=m2edxkb6mq.fsf@numbchild@gmail.com \
--to=numbchild@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@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).