From: Antonio Piccolboni <piccolbo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: undefined cross-ref since pandoc v3
Date: Sat, 28 Jan 2023 10:04:15 -0800 (PST) [thread overview]
Message-ID: <1534fc3d-7bf6-42ce-a9a2-a11c828bb2c3n@googlegroups.com> (raw)
In-Reply-To: <b47fac54-8ebe-4eb0-9b86-a1e82fa4ae8fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2876 bytes --]
This is being addressed in the issue referenced above
https://github.com/pandoc/lua-filters/issues/261
On Friday, January 27, 2023 at 3:52:14 PM UTC-8 Antonio Piccolboni wrote:
> I opened issues in both pandoc-crossref and lua-filters
> https://github.com/pandoc/lua-filters/issues/261
> https://github.com/lierdakil/pandoc-crossref/issues/371
> I provided a MRE in there.
>
> On Friday, January 27, 2023 at 3:15:54 PM UTC-8 Antonio Piccolboni wrote:
>
>> Good point, I use brew without thinking too much about it, but I checked
>> and it's the latest 0.3.15.0. In the release page it does mention there
>> have been changes in figure handling and to be on the look for bugs. Maybe
>> I should report there.
>>
>> On Friday, January 27, 2023 at 2:52:31 PM UTC-8 Bastien Dumont wrote:
>>
>>> Do you have the latest version of pandoc-crossref? It has been updated
>>> for pandoc 3 last week (see here:
>>> https://github.com/lierdakil/pandoc-crossref/releases/tag/v0.3.15.0).
>>>
>>> Le Friday 27 January 2023 à 10:19:43AM, Antonio Piccolboni a écrit :
>>> > Hi,
>>> > just upgraded from 2.18 to 3.0.2 and running it on an existing project
>>> I have
>>> > some broken crossref. They are all graphviz graphs generated with
>>> > diagram-generator.lua. This is a snippet
>>> >
>>> >
>>> > ... to the subgraphs in @fig:cyclomatic.
>>> >
>>> > ```{.graphviz #fig:cyclomatic caption="Graphs corresponding to `if`
>>> and `while`
>>> > statements resp."}
>>> > ...
>>> > ```
>>> > I read the release notes but I can't find anything that relates to
>>> this. Any
>>> > suggestions? Thanks
>>> >
>>> >
>>> > Antonio
>>> >
>>> > --
>>> > 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 [1]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>>> > To view this discussion on the web visit [2]
>>> https://groups.google.com/d/msgid/
>>> > pandoc-discuss/5ce59ce6-b0df-4cc0-99e0-26f221b0db72n%
>>> 40googlegroups.com.
>>> >
>>> > References:
>>> >
>>> > [1] mailto:pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>>> > [2]
>>> https://groups.google.com/d/msgid/pandoc-discuss/5ce59ce6-b0df-4cc0-99e0-26f221b0db72n%40googlegroups.com?utm_medium=email&utm_source=footer
>>>
>>>
--
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/1534fc3d-7bf6-42ce-a9a2-a11c828bb2c3n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 5784 bytes --]
prev parent reply other threads:[~2023-01-28 18:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 18:19 Antonio Piccolboni
[not found] ` <5ce59ce6-b0df-4cc0-99e0-26f221b0db72n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-01-27 22:52 ` Bastien DUMONT
2023-01-27 23:15 ` Antonio Piccolboni
[not found] ` <6aba8682-69d8-47aa-8101-e6e31b3b2a92n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-01-27 23:52 ` Antonio Piccolboni
[not found] ` <b47fac54-8ebe-4eb0-9b86-a1e82fa4ae8fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-01-28 18:04 ` Antonio Piccolboni [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=1534fc3d-7bf6-42ce-a9a2-a11c828bb2c3n@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).