From: Cev Ing <ceving-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: How to format visible reference links?
Date: Sat, 11 Nov 2023 10:20:21 -0800 (PST) [thread overview]
Message-ID: <7ab32601-e03d-4587-a563-e329a1987781n@googlegroups.com> (raw)
In-Reply-To: <CAEe_xxgZLE-AHfxvWQ1yFsMX_WRwQq1Yf0DeyzCCeEZzS5xJ_A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1044 bytes --]
William Lupton schrieb am Samstag, 11. November 2023 um 18:20:32 UTC+1:
To prevent this, you could escape the opening square brackets like this
(I've also put the URLs in angle brackets):
### Referenzen
- \[1]: <https://www.youtube.com/@johnwitulski18> "John Witulski"
- \[2]: <https://www.youtube.com/watch?v=Rl70mXyDxII> "Vorlesung
Compilerbau (5) - Bottom-Up Parsing"
- \[3]: <https://cisco.github.io/ChezScheme/> "Chez Scheme"
I tried that, but then the reference-links stop working. I do not want to
prevent the reference-links, instead I want both: working links in the text
and a list of all links at the bottom.
--
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/7ab32601-e03d-4587-a563-e329a1987781n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1938 bytes --]
next prev parent reply other threads:[~2023-11-11 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 16:36 Cev Ing
[not found] ` <bce4c86a-f712-4204-9477-43003279a07en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-11-11 17:20 ` 'William Lupton' via pandoc-discuss
[not found] ` <CAEe_xxgZLE-AHfxvWQ1yFsMX_WRwQq1Yf0DeyzCCeEZzS5xJ_A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-11-11 18:20 ` Cev Ing [this message]
[not found] ` <7ab32601-e03d-4587-a563-e329a1987781n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-11-11 18:51 ` 'William Lupton' via pandoc-discuss
[not found] ` <CAEe_xxhCgWUKDBB8HmPdAkbTWk+C2N0OD5F8Yah41qGSB8kdAQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-11-11 19:20 ` Cev Ing
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=7ab32601-e03d-4587-a563-e329a1987781n@googlegroups.com \
--to=ceving-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).