From: Francisco Lopes <francisco.mailing.lists-iwoE/Jjr5LLQT0dZR+AlfA@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: markdown -> markdown: How to avoid link inline/reference, implicit/explicit changes?
Date: Wed, 6 Sep 2017 21:45:40 -0700 (PDT) [thread overview]
Message-ID: <a5307436-944c-4842-8257-4f96224576c8@googlegroups.com> (raw)
In-Reply-To: <ae93e47e-0255-4bfb-861c-0f2316282c8f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 906 bytes --]
Em quinta-feira, 7 de setembro de 2017 01:38:15 UTC-3, Kolen Cheung
escreveu:
>
> No, I don't think it can be done. The information on the name of the
> reference is lost when converted into the AST.
Sad, the other two options are bad: long URLs mixed with text, long named
implicit references (the link can be several words).
--
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/a5307436-944c-4842-8257-4f96224576c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 429676 bytes --]
next prev parent reply other threads:[~2017-09-07 4:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 16:51 Francisco Lopes
[not found] ` <d2ce3cec-aaa3-4805-9fc2-4029aee86e0c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-07 4:38 ` Kolen Cheung
[not found] ` <ae93e47e-0255-4bfb-861c-0f2316282c8f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-07 4:45 ` Francisco Lopes [this message]
[not found] ` <a5307436-944c-4842-8257-4f96224576c8-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-07 4:49 ` Francisco Lopes
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=a5307436-944c-4842-8257-4f96224576c8@googlegroups.com \
--to=francisco.mailing.lists-iwoe/jjr5llqt0dzr+alfa@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).