public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Antonio Piccolboni <piccolbo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: quoted atoms highlighted as errors in prolog
Date: Thu, 13 Oct 2022 14:40:39 -0700 (PDT)	[thread overview]
Message-ID: <18f7f4df-2bc8-4244-848c-c07fef627f51n@googlegroups.com> (raw)
In-Reply-To: <D385346A-F711-4D6C-B6CC-68454AC03B8A-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 1195 bytes --]

New to Kate, but AFAICT no problem there (saved code in .prolog file, atom 
highlighted in green, not bold red). Looking into skylighting



On Thursday, October 13, 2022 at 1:37:29 PM UTC-7 fiddlosopher wrote:

> 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 <picc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 
> wrote:
> > 
> > Hi
>
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/18f7f4df-2bc8-4244-848c-c07fef627f51n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 1825 bytes --]

  parent reply	other threads:[~2022-10-13 21:40 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
     [not found]     ` <D385346A-F711-4D6C-B6CC-68454AC03B8A-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-10-13 21:40       ` Antonio Piccolboni [this message]
     [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=18f7f4df-2bc8-4244-848c-c07fef627f51n@googlegroups.com \
    --to=piccolbo-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).