From: Timothy <firstname.lastname@example.org> To: Bruce D'Arcus <email@example.com> Cc: Tim Cross <firstname.lastname@example.org>, email@example.com Subject: Re: [PATCH] ox-md.el export code blocks using grave accents. Date: Tue, 27 Apr 2021 18:18:44 +0800 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <CAF-FPGPFFj0_9ufGZnmqfqz1GdVUx=uyTh-ftcNXABwNw3aRHQ@mail.gmail.com> Bruce D'Arcus <email@example.com> writes: > On Sat, Jan 30, 2021, 6:29 PM Tim Cross <firstname.lastname@example.org> wrote: > >> There are no precise standards for markdown, but org states in the >> manual that the version of markdown it supports is that defined at >> http://daringfireball.net/projects/markdown > > Perhaps at some point it would make sense to change to this, which is > much more precisely specified: > > https://commonmark.org/ The only change I'd think would be worthwhile, is to complicate ox-md by introducing the concept of styles/presets. Even just commonmark has multiple ways you can do things (backticks and spaces for code), and I'd think supporting a set like: Gruber's original, commonmark, and GFM would make sense. Alternatively, we can leave that to other backends like ox-gfm. Basically: markdown is a mess and I'm not sure what would be a good course of action. -- Timothy
next prev parent reply other threads:[~2021-04-27 10:20 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-30 21:57 Rodrigo Morales 2021-01-30 22:51 ` Tim Cross 2021-01-30 23:53 ` Rodrigo Morales 2021-04-27 8:43 ` Bastien 2021-04-27 10:03 ` Bruce D'Arcus 2021-04-27 10:18 ` Timothy [this message] 2021-04-27 11:32 ` Nicolas Goaziou -- strict thread matches above, loose matches on Subject: below -- 2021-01-29 3:43 Rodrigo Morales 2021-01-29 3:47 ` Rodrigo Morales 2021-01-31 19:55 ` Rodrigo Morales
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 List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH] ox-md.el export code blocks using grave accents.' \ /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
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git 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 read-only IMAP folder(s) and NNTP newsgroup(s).