From: ThomasH <therch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Line number of input file
Date: Wed, 3 May 2023 22:56:43 -0700 (PDT) [thread overview]
Message-ID: <e57d7ea9-cdc6-4cad-b23e-babc48283893n@googlegroups.com> (raw)
In-Reply-To: <87o7n1c2oy.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1371 bytes --]
Ah, ok, thanks.
On Wednesday, May 3, 2023 at 9:08:22 AM UTC+2 Albert Krewinkel wrote:
>
> ThomasH <the...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > Is there a way to get at the current line number of the current input
> > file in a Lua filter?
> >
> > I can get the input file via PANDOC_STATE.input_files alright, but
> > what about the input line?
> >
> > I understand that Lua filters work on Pandoc ASTs, so the raw string
> > input is already transformed. I used to save input line numbers with
> > AST nodes when I wrote parsers. Is there such facility in Pandoc's
> > ASTs? Writing a custom reader?
>
> The CommonMark parser can be used with the `sourcepos` extension.
> Enabling the extension will add positional information via div and span
> attributes. The other parsers in pandoc don't have a comparable feature.
>
>
> --
> Albert Krewinkel GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
>
--
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/e57d7ea9-cdc6-4cad-b23e-babc48283893n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2002 bytes --]
prev parent reply other threads:[~2023-05-04 5:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 6:16 ThomasH
[not found] ` <4b09ae5e-99be-4772-b65d-62c5ffe68ccfn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-03 7:03 ` Albert Krewinkel
[not found] ` <87o7n1c2oy.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-05-04 5:56 ` ThomasH [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e57d7ea9-cdc6-4cad-b23e-babc48283893n@googlegroups.com \
--to=therch-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).