Comments (6)
This is not an error but a design choice as explained in the README.
Two workarounds come into mind immediately
iex(7)> text = ~s/Hello `sign\n \\* one`/
"Hello `sign\n \\* one`"
iex(8)> Earmark.to_html text
"<p>Hello `sign\n * one`</p>\n"
iex(9)> text = ~s/Hello `sign\n * one`/
"Hello `sign\n * one`"
iex(10)> Earmark.to_html text
"<p>Hello `sign\n * one`</p>\n"
iex(11)> text = ~s/Hello `sign\n * one`/
Not sure how the second renders. Maybe it is just best to rearrange the doc so that the line does not start with an *
which is more readable anyway.
For what it is worth, about 30% of the markdown implementations on Babelmark (http://johnmacfarlane.net/babelmark2/?text=%60sign%0A*+expression%60) agree with Dave's interpretation.
from earmark.
oops that reveals another issue
from earmark.
@tubedude sorry if I missread your issue, you meant #49 not the <ul> issue
right?
from earmark.
Yes @RobertDober I think this issue is related to the backquotes enclosing a multiline text.
I agree with you that this issue and #49 are the same.
from earmark.
@pragdave I just pushed a development branch that fixes #48, #49 & #51. However the code is not one that I would happily merge into master.
I need your wisdom here :). But is this the right place to discuss the code quality and design choices I have made? (or rather not made, I tried to respect your design as much as possible)
from earmark.
Closed with 55828d1
from earmark.
Related Issues (20)
- from_file! ignores the options if not a .eex file is passed HOT 2
- All legal options do not seem to be recognized by the Earmark CLI right now HOT 1
- v1.4.41 regression: module :string_lexer is not available HOT 18
- ast back to markdown HOT 9
- Duplicated modules using earmark and earmark_parser HOT 5
- I'd like to maintain earmark HOT 6
- Announcement for change of maintainer HOT 2
- Can't find Earmark.Parser.HtmlRenderer
- Typespecs edits
- Pure link feature does not support inline links without a protocol HOT 3
- Warning on Elixir 1.16 HOT 2
- Applying bold, italics and strikethrough simultaneously is handled inconsistently
- Which flavour/spec of markdown is used by earmark?
- Single ~ is not accepted for strikethrough HOT 2
- Parser situation is confusing HOT 11
- [1.4.46] Parser crash on `Earmark.as_ast("\\[{:}")` HOT 5
- The CLI outputs the input device's name to standard output
- Earmark and EarmarkParser need better documentation about the split. HOT 2
- Earmark crashes (like EarmarkParser) on `"\\[{:}" `
- Proposition: Backport of optional math syntax from EarmarkParser
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from earmark.