From: mb21 <mauro.bieg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Discussion needed—How should pandoc handle when meatada in YAML collide with command line option
Date: Mon, 23 Jan 2017 02:13:36 -0800 (PST) [thread overview]
Message-ID: <679bf64d-3de1-48e3-b738-0e9059c69a98@googlegroups.com> (raw)
In-Reply-To: <20170118112524.GB44054-BKjuZOBx5Kn2N3qrpRCZGbhGAdq7xJNKhPhL2mjWHbk@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 798 bytes --]
Okay, I've started a wiki page to keep track of the major changes we've
been thinking about.
https://github.com/jgm/pandoc/wiki/Roadmap
The idea is not to include all those in pandoc 2.0 but maybe we manage to
do a few...
--
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/679bf64d-3de1-48e3-b738-0e9059c69a98%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 1321 bytes --]
next prev parent reply other threads:[~2017-01-23 10:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 3:18 Kolen Cheung
[not found] ` <836ca2d4-6e39-4f7e-b227-69dc06be6f15-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-10-29 17:24 ` BP Jonsson
[not found] ` <CAFC_yuQZfyYuP6LzVtv02pVkr92Vx6zATosAdXbm+BCbxeTMMw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-31 4:13 ` Kolen Cheung
[not found] ` <bd8aea27-38c3-4ace-af2e-6603a64fb977-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-10-31 18:14 ` Melroch
2016-12-01 11:55 ` Kolen Cheung
[not found] ` <CADAJKhBWjp7-7-JCrqZXnkaOw8xRtDDv-tCUos29=T1JOTOWkg@mail.gmail.com>
[not found] ` <CADAJKhA7miFDtn5dOxtFw5VF7TwQMDiXs=8pnrKoOUuVhjoRgQ@mail.gmail.com>
[not found] ` <CADAJKhA7miFDtn5dOxtFw5VF7TwQMDiXs=8pnrKoOUuVhjoRgQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-02 15:36 ` Melroch
[not found] ` <CADAJKhCfDzDaQYSn=iNzM0XXEpisontg=LxrOadmHD6_6aNriw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-02 22:42 ` BP Jonsson
2016-12-03 0:28 ` Kolen Cheung
[not found] ` <089593aa-75c3-42fb-9b94-1cf0c01643cd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-12-03 0:38 ` Melroch
[not found] ` <CADAJKhCkSC80BR8NDbFKArmRR=80DxxRXQYeEVcBVhiCgxWgYw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-03 1:21 ` Kolen Cheung
[not found] ` <f57e9537-1701-4e48-8d1f-c3d9c43af24f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-12-04 22:32 ` Melroch
[not found] ` <CADAJKhDHskio7KYbEo0yXMvLQL+WYYWyh_gO3HNqwCTVRTJB8g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-05 1:13 ` Kolen Cheung
[not found] ` <8d8167cf-894c-4dd4-8b1b-1fe8b49b3258-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-17 17:54 ` mb21
[not found] ` <aed26351-9296-42f2-9711-94f029fb8b0d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-17 18:24 ` Kolen Cheung
[not found] ` <7bcf5965-a2fa-41d5-817e-bc27aeba7c7d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-18 11:03 ` John MacFarlane
2017-01-18 11:25 ` John MacFarlane
[not found] ` <20170118112524.GB44054-BKjuZOBx5Kn2N3qrpRCZGbhGAdq7xJNKhPhL2mjWHbk@public.gmane.org>
2017-01-23 10:13 ` mb21 [this message]
[not found] ` <679bf64d-3de1-48e3-b738-0e9059c69a98-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-23 10:23 ` John MacFarlane
[not found] ` <20170123102338.GL1889-BKjuZOBx5Kn2N3qrpRCZGbhGAdq7xJNKhPhL2mjWHbk@public.gmane.org>
2017-01-23 10:38 ` mb21
[not found] ` <5038f42b-77c9-4e63-a1ed-fbea1342828c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-23 10:50 ` Kolen Cheung
2017-01-17 18:47 ` Albert Krewinkel
2017-01-18 11:23 ` John MacFarlane
2018-02-01 7:17 ` tolot27
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=679bf64d-3de1-48e3-b738-0e9059c69a98@googlegroups.com \
--to=mauro.bieg-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).