From: "'Charles Teague' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Pandoc 3 Change in commonmark extensions
Date: Tue, 21 Feb 2023 10:34:54 -0800 (PST) [thread overview]
Message-ID: <be4647e6-a36d-4ae0-a2be-4c440ff9d170n@googlegroups.com> (raw)
In-Reply-To: <ABAF0A22-27DB-423F-9596-C8146EEF1C69-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2433 bytes --]
That is exactly the issue, ty!
On Tuesday, February 21, 2023 at 12:41:56 PM UTC-5 John MacFarlane wrote:
> The documented syntax is
>
> pandoc --list-extensions=commonmark
>
> That should give you the right list.
>
> Without the `=`, pandoc is giving you extensions for the default format,
> and treating `commonmark` as an additional argument which is ignored.
>
> The `=` is necessary here (unlike with `--to`) because the argument is
> optional. (If the `=` is not used, the option parser assumes you're not
> providing an argument, because otherwise there'd be an ambiguity.)
>
> > On Feb 20, 2023, at 8:21 AM, 'Charles Teague' via pandoc-discuss <
> pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> wrote:
> >
> > Starting in Pandoc 3, I've noticed that the commonmark format appears to
> have a different set of extensions when enumerated via:
> >
> > `pandoc --list-extensions commonmark`
> >
> > The changes are:
> >
> > Removed:
> > -amuse
> > -attributes
> > -element_citations
> > -empty_paragraphs
> > -epub_html_exts
> > -mark
> > -markdown_attribute
> > -native_numbering
> > -ntb
> > -raw_markdown
> > -sourcepos
> > -styles
> > -xrefs_name
> > -xrefs_number
> >
> > Added:
> > -wikilinks_title_after_pipe
> > -wikilinks_title_before_pipe
> >
> > The removes were unexpected to us (things like `-sourcepos` appear to
> work even though they are not listed in the output from that command).
> Before I open an issue I just wanted to double check that this wasn't
> expected and perhaps I just misunderstood something...
> >
> > Thanks
> >
> > Charles
> >
> > --
> > 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/e7c74574-45ce-43fa-a0b9-f3e70571b45en%40googlegroups.com
> .
>
>
--
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/be4647e6-a36d-4ae0-a2be-4c440ff9d170n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3645 bytes --]
prev parent reply other threads:[~2023-02-21 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 16:21 'Charles Teague' via pandoc-discuss
[not found] ` <e7c74574-45ce-43fa-a0b9-f3e70571b45en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-02-21 17:41 ` John MacFarlane
[not found] ` <ABAF0A22-27DB-423F-9596-C8146EEF1C69-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-02-21 18:34 ` 'Charles Teague' via pandoc-discuss [this message]
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=be4647e6-a36d-4ae0-a2be-4c440ff9d170n@googlegroups.com \
--to=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).