From: Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Reference link support in AST (for Quarto's Visual Editor)?
Date: Wed, 8 Feb 2023 10:50:49 -0500 [thread overview]
Message-ID: <5680a672-b7b0-d7aa-b35b-34693d3b2022@reagle.org> (raw)
I've been looking forward to Quarto's stand-alone Visual Editor as a pandoc-friendly multi-line table supporting editor. However, it rewrites my carefully specified reference links and they wrote:
> We currently aren't able to support reference links because when Pandoc parses the page they are all resolved into "real" links (i.e. the Pandoc AST doesn't have the concept of a reference link, and since our editor is really editing the AST not the markdown text, there isn't any way for us to read or write them).
https://github.com/quarto-dev/quarto/issues/42
Has any thought been given to this?
—Joseph
--
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/5680a672-b7b0-d7aa-b35b-34693d3b2022%40reagle.org.
next reply other threads:[~2023-02-08 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 15:50 Joseph Reagle [this message]
[not found] ` <5680a672-b7b0-d7aa-b35b-34693d3b2022-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2023-02-08 17:32 ` John MacFarlane
[not found] ` <9A64C448-20CB-4E7B-9739-61AD4730DB89-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-02-09 14:28 ` Joseph Reagle
[not found] ` <7241d44d-dbe4-15f4-c1c5-a46ff6c069da-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2023-02-09 14:29 ` Joseph Reagle
2023-02-09 16:08 ` 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=5680a672-b7b0-d7aa-b35b-34693d3b2022@reagle.org \
--to=joseph.2011-t1oy19wchswdnm+yrofe0a@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).