public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: quoted atoms highlighted as errors in prolog
Date: Thu, 13 Oct 2022 13:37:23 -0700	[thread overview]
Message-ID: <D385346A-F711-4D6C-B6CC-68454AC03B8A@gmail.com> (raw)
In-Reply-To: <34ee4a2d-b80d-4a44-acca-c68fc55fb380n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

I don't know, but pandoc's highlighting is based on KDE syntax definitions.
So first step is to see if you get a similar result in the Kate editor.
If you do, the problem is with the prolog.xml definition we build on, and it
should be reported upstream.  If not, the problem may lie in pandoc's
(really skylighting's) implementation of the KDE syntax definitions.
See jgm/skylighting - the README.md there has more information.

> On Oct 13, 2022, at 1:03 PM, Antonio Piccolboni <piccolbo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> 
> Hi


  parent reply	other threads:[~2022-10-13 20:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-13 20:03 Antonio Piccolboni
     [not found] ` <34ee4a2d-b80d-4a44-acca-c68fc55fb380n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-10-13 20:37   ` John MacFarlane [this message]
     [not found]     ` <D385346A-F711-4D6C-B6CC-68454AC03B8A-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-10-13 21:40       ` Antonio Piccolboni
     [not found]         ` <18f7f4df-2bc8-4244-848c-c07fef627f51n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-10-13 21:47           ` Antonio Piccolboni
     [not found]             ` <da61c885-da73-4ff3-8d92-72df8510bdf3n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-10-13 21:48               ` Antonio Piccolboni
2022-10-13 22:50               ` John MacFarlane

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=D385346A-F711-4D6C-B6CC-68454AC03B8A@gmail.com \
    --to=fiddlosopher-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).