From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Changing names of some extensions to reflect manual pages or some hierarchy
Date: Fri, 30 Sep 2022 09:25:00 -0700 [thread overview]
Message-ID: <5EDB63AD-A466-4EEB-AEE0-068283F5E679@gmail.com> (raw)
In-Reply-To: <3a26c3b6-3557-4b2b-a8da-21b9c39fa3c9n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Perhaps, if we were starting from scratch. But changing this now would cause too much pain in the ecosystem.
> On Sep 30, 2022, at 4:22 AM, lucabal...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org <lucabalsanelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> Hi,
>
> one of the most difficult things for me in using pandoc is to learn extensions and remember their names.
>
> I was wondering if it wouldn't be better to rename some of them differently. In particular it would be useful to reverse their names, for example:
>
> + simple_tables -> tables_simple
> + multiline_tables -> tables_multiline
> + grid_tables -> tables_grid
> + pipe_tables -> tables_pipe
>
> so for example, the output of `pandoc --list-extensions=markdown` would be
>
> ```
> [OMISSIS]
> +table_captions
> +tables_multiline
> +tables_pipe
> +tables_simple
> [OMISSIS]
> ```
>
> and so on for many other. I know this may break things in scripts, but it would simplify the use of extensions a lot in my opinion.
>
> Thanks,
> Luca
>
> --
> 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/3a26c3b6-3557-4b2b-a8da-21b9c39fa3c9n%40googlegroups.com.
next prev parent reply other threads:[~2022-09-30 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 11:22 lucabal...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
[not found] ` <3a26c3b6-3557-4b2b-a8da-21b9c39fa3c9n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-09-30 16:25 ` John MacFarlane [this message]
[not found] ` <5EDB63AD-A466-4EEB-AEE0-068283F5E679-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-09-30 19:26 ` Luca Balsanelli
2022-09-30 16:43 ` BPJ
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=5EDB63AD-A466-4EEB-AEE0-068283F5E679@gmail.com \
--to=fiddlosopher-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).