emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sébastien Miquel" <sebastien.miquel@posteo.eu>
To: Timothy <tecosaur@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Why is there no inline-src syntax highlighting?
Date: Mon, 29 Mar 2021 15:58:54 +0200	[thread overview]
Message-ID: <4ef07c13-482d-734c-aa17-479439493c68@posteo.eu> (raw)
In-Reply-To: <87o8f2kta7.fsf@gmail.com>


I don't use inline src blocks, but your work makes me want to start !

Timothy writes:
> there's just one thing I
> haven't been able to work out --- how to have font-lock apply to
> *multiple*  inline src blocks on one line.

With multiple inline src blocks that each have a result part,
fontification appears to work.

I think there are these two issues with the code :
  - When an inline src blocks has no matching result part,
    `org-fontify-inline-src-blocks-1` returns nil. It should return t
    instead, then it will be called again, to fontify the next block.
  - If an inline src block without results is followed by a src block
    with results, your function skips over the second src block.
    Perhaps you should assume that only whitespace separates a src
    block and its results (this is already assumed for subsequent
    evaluations of the block  to replace the results).


Sébastien Miquel

  reply	other threads:[~2021-03-29 13:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-14 10:19 Why is there no inline-src syntax highlighting? Timothy
2021-03-14 15:00 ` Eric S Fraga
2021-03-14 18:18   ` Colin Baxter
2021-03-14 18:27     ` Timothy
2021-03-14 18:36       ` Colin Baxter
2021-03-14 18:29   ` Timothy
2021-03-15  6:07 ` Andreas Leha
2021-03-29 13:01 ` Timothy
2021-03-29 13:58   ` Sébastien Miquel [this message]
2021-03-29 14:53     ` Timothy
2021-03-29 13:59   ` 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:

  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=4ef07c13-482d-734c-aa17-479439493c68@posteo.eu \
    --to=sebastien.miquel@posteo.eu \
    --cc=emacs-orgmode@gnu.org \
    --cc=tecosaur@gmail.com \


* 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


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