emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Timothy <tecosaur@gmail.com>
Cc: emacs-orgmode@gnu.org, Tim Cross <theophilusx@gmail.com>,
	Bruce D'Arcus <bdarcus@gmail.com>
Subject: Re: [PATCH] ox-md.el export code blocks using grave accents.
Date: Tue, 27 Apr 2021 13:32:17 +0200	[thread overview]
Message-ID: <87v988j73y.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87a6pk58u3.fsf@gmail.com> (Timothy's message of "Tue, 27 Apr 2021 18:18:44 +0800")


Timothy <tecosaur@gmail.com> writes:

> 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.

That is the idea. "ox-md" is here to do the boring tasks, while being as
neutral as possible. There no need to handle specific syntax since you
can easily create a derived back-end.

> Basically: markdown is a mess and I'm not sure what would be a good
> course of action.

Nicolas Goaziou

  reply	other threads:[~2021-04-27 11:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-30 21:57 [PATCH] ox-md.el export code blocks using grave accents 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
2021-04-27 11:32       ` Nicolas Goaziou [this message]
  -- 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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v988j73y.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=bdarcus@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tecosaur@gmail.com \
    --cc=theophilusx@gmail.com \


* 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.
Code repositories for project(s) associated with this public inbox


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).