Earmark - Elixir's Markdown Converter

Your Libraries & OS Mentoring Libraries
,
87

and to answer this question: No not right now, of course the meta part of the AST could be used for that but I would hate to load this burden on ex_doc so maybe an Option.

Much work, no time, alas

88

Thanks for the advice. Stealing the above cited Livebook code and retrofiting it onto Floki AST shall satisfy my immediate need. I asked to see if there is any grand plan in place already.

89

Nope, sorry

90

Happy New Year

I just released a quickfix release for EarmarkParser v1.4.19

1.4.19 2022-01-07

  • Typos
    Kudos to kianmeng

  • Footnotes fixed and upgraded(#26)

    Footnotes are now a superset of GFM Footnotes. This implies some changes

    • Footnote definitions ([^footnote_id]) must come at the end of your document (GFM) - Footnotes that are not referenced are not rendered anymore (GFM)
    • Footnote definitions can contain any markup with the exception of footnote definitions

N.B.
Footnotes are not downwards compatible with 1.4.18 and therefore no accompaning Earmark Release will be done (ex_doc does not use footnotes)
hopefully 1.5.0 will come out soon with breaking list changes too

1 Like
91

I appologize to all Earmark users I forgot that the incompatible release of EarmarkParser will cause problems on Earmark

please upgrade to 1.4.20 which assures the usage of the compatible EarmarkParser version 1.4.18

Earmark 1.4.20 2022-01-08

  • Fix EarmarkParser version to 1.4.18 as the 1.4.x branch is not supporting Earmark anymore (1.5 should hopefully)
92

Erratum on EarmarkParser Release Note

1.4.19 2022-01-07

1 Like
93

Earmark Parser 1.4.20 released

Synopsis

(although the original Synapsis deserves to be conserved)

This drops support for Elixir 1.10 and incorporates some small changes for the new admonition support for ex_doc which have been gracefully provided by @josevalim

1.4.20 2022-02-21

1 Like
94

# Earmark 1.4.21 release delayed

Earmark 1.5.0-pre released

1.5.0-pre 2022-02-21

This introduces regressions concerning nested lists and sophisticated edge cases, but introduces the following features as well as all features of EarmarkParser 1.4.19 & 1.4.20

The will be regressions fixed in 1.5.0

1 Like
95

I just released a hotfix for missing paragraph context after indented code blocks Alternative header syntax after code is "invalid" · Issue #98 · RobertDober/earmark_parser · GitHub

All three links are the same, sorry

EarmarkParser Release 1.4.21 2022-03-13

Earmark Release 1.5.0-pre1 2022-03-13

2 Likes
96

I just released

EarmarkParser 1.4.22

and

Earmark 1.4.21

EarmarkParser 1.4.22 fixes the list regressions (as 1.5 will just not be ready soon)
and thus Earmark can be used with ex_doc again (c.f. Hopefully this shall take care of the issue reported here by RobertDober · Pull Request #29 · surface-ui/surface_catalogue · GitHub)

For completeness the somehow redundant RELEASE NOTES

EarmarkParser

1.4.22 2022-03-14

Fixes all List Regressions introduced in 1.4.19

GFM support for lists remain limited (spaced and tight lists are not 100% compliant) but is better than in 1.4.18

Earmark

1.4.21 2022-03-14

Takes advantage of the fixed regressions in EarmarkParser release 1.4.22 and therefore makes all
features of the latest EarmarkParser release available

2 Likes
97

I just fixed two other regressions in lists in this release

Earmark 1.4.23 2022-03-16

Two more list regressions fixed

  • multi line inline code was ignored in the body parts of lists

  • spaced lists with inline code in their bodies (single and multiline) were rendered tightly (no surrounding <p>...</p>

  • oh and a lot of dead code elimination and a 98% code coverage

Earmark 1.4.22 2022-03-16

for EarmarkParser v1.4.23

1 Like
98

A small bug concerning footnotes is fixed in:

EarmarkParser 1.4.24 2022-03-20

  • Single worded footnote definitions where shadowed by ID Definitions, the tiebreak was resolved in favor of Footnotes as ID Definitions do not need, and might as a matter of fact almost never, to start with a ^
    Related Issue

  • Unused import warning removed

The corresponding Earmark version 1.4.23 was released too

3 Likes
99

A release to integrate the fix for long lines inside code fences

EarmarkParser 1.4.25 2022-03-24

And the according Earmark release

Earmark 1.4.24 2022-03-24

for EarmarkParser v1.4.25

1 Like
100

I just released

Earmark 1.4.25 2022-05-01

Examples for this can be found
here(:replace)
and
here(change mapper function)

N.B. No changes in the parser only enhancements for AST Transformation (hence no new release of EarmarkParser)

1 Like
101

I just released

EarmarkParser 1.4.26 2022-06-15

102

and without further ado

Earmark 1.4.26 2022-06-15

Accompanying release of EarmarkParser 1.4.26

2 Likes
103

I just released

Earmark 1.4.27 2022-08-11

this can hurt you in some special cases if you use the global Application config with :earmark which you should not do but I considered it nevertheless a bug as pointed out correctly in the ticket: Config — Elixir v1.13.4.

No change on EarmarkParser

2 Likes
104

I just released

EarmarkParser 1.4.27 2022-09-30

2 Likes
105

and also

Earmark 1.4.29

which allows the usage of the sub_sup: true option from EarmarkParser v1.4.27

1 Like
106

Thanks! I’m integrating this version with Lambdapad and it’s working fine :slight_smile:

1 Like