Hello,
Timothy 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
Bruce D'Arcus writes:
> On Sat, Jan 30, 2021, 6:29 PM Tim Cross 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
On Sat, Jan 30, 2021, 6:29 PM Tim Cross 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,
Tim Cross writes:
> I don't think this patch is correct.
I'm marking it as "canceled" right now, thanks.
Please, omit this duplicated thread. It has already been discussed.
This thread was created due to an error of mine.
On Thu, 28 Jan 2021 at 22:51, Rodrigo Morales
wrote:
>
> Sorry for not attaching the files. Here they are.
>
>
> --
> Greetings,
> Rodrigo Morales.
>
[PATCH] ox-md.el export code blocks using grave accents.
This patch includes the following changes in =ox-md.el=
+ =org-md-example-block= now exports code blocks using triple grave
accents instead of four spaces of indentation. This has been done
for two main reasons:
1. To be able
Sorry for not attaching the files. Here they are.
# Table of Contents
When exporting the following code block using indentation, it is not
possible to know where the source code ends and the results of
evaluation starts.
echo "echo ab"
echo "seq 1 2"
echo ab
seq 1 2
The
Tim Cross writes:
> I don't think this patch is correct.
>
> From your explanation, I suspect what you really need is to use the
> github flavoured markdown package available as ox-gfm on MELPA rather
> than the default ox-md package in org mode.
Thank you very much for the detailed
I don't think this patch is correct.
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 - which uses the indentation
style for code blocks, not the style. Note
This patch includes the following changes in =ox-md.el=
+ =org-md-example-block= now exports code blocks using triple grave
accents instead of four spaces of indentation. This has been done
for two main reasons:
1. To be able to include the language so that Markdown engines can
10 matches
Mail list logo