From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Cc: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
Subject: Re: Summer project ideas
Date: Thu, 28 Jan 2021 10:22:03 -0800 [thread overview]
Message-ID: <m2a6ss9b1w.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
In-Reply-To: <CADAJKhCT0mpp7Tvj4xMn9ToZUktvob-QtTcZK9Gf7DMRRetabA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
The thing I've always resisted about pandoc-crossref syntax is
the use of English-derived keywords for labels. Perhaps there's
not a good way to avoid that, but it would be something I'd want
to look inot.
BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> I guess that some of the pandoc-crossrefs code might be useful. At least I
> hope that any built-in reference handling will stay as close to
> pandoc-crossrefs's syntax and interface as possible so that old files
> written with pandoc-crossrefs in mind will work with as little change as
> possible (hopefully none.)
next prev parent reply other threads:[~2021-01-28 18:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 21:21 Albert Krewinkel
[not found] ` <87bldavzy2.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2021-01-28 1:45 ` John MacFarlane
[not found] ` <m235ylal7f.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-01-28 11:03 ` AW: " denis.maier-FfwAq0itz3ofv37vnLkPlQ
[not found] ` <1fedfa2a9a174255a781ef43c5b03912-FfwAq0itz3ofv37vnLkPlQ@public.gmane.org>
2021-01-28 17:46 ` BPJ
[not found] ` <CADAJKhCT0mpp7Tvj4xMn9ToZUktvob-QtTcZK9Gf7DMRRetabA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-01-28 18:22 ` John MacFarlane [this message]
[not found] ` <m2a6ss9b1w.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-01-28 19:55 ` BPJ
2021-01-29 14:03 ` Albert Krewinkel
[not found] ` <875z3fu9fc.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2021-01-29 17:58 ` John MacFarlane
[not found] ` <m2ft2j62wi.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-01-30 8:35 ` Albert Krewinkel
[not found] ` <8735yiu8jp.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2021-01-31 1:40 ` John MacFarlane
2021-02-17 1:01 ` John MacFarlane
[not found] ` <m21rdf8q2z.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-02-17 18:35 ` John MacFarlane
2021-01-29 18:59 ` Julien Dutant
[not found] ` <6036a733-df54-4985-bbab-beb743c032adn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-01-29 20:39 ` John MacFarlane
2021-01-30 9:00 ` Albert Krewinkel
[not found] ` <871re2u7dw.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2021-01-31 0:37 ` Julien Dutant
2021-02-14 8:07 ` Albert Krewinkel
[not found] ` <87r1ljax8g.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2021-02-14 13:09 ` jcr
[not found] ` <4c65af87-daee-4c11-9f03-f95ac9f69146n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-02-14 14:44 ` Albert Krewinkel
2021-01-31 18: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=m2a6ss9b1w.fsf@MacBook-Pro.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org \
--cc=melroch-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).