Hello,
First thanks for the great mailing list service. Since I'm just
talking to myself here this will be my last post on markdown list
(never say never ;-) Anyways, they never come back, don't they?
If you follow along there are different ways to "fix" markdown:
1) Create your own flavor and rules e.g. kramdown, multimarkdown, etc.
2) Try to nail down all rules in "basic" markdown e.g. CommonMark
3) Why not evolve markdown?
What's evolution? Why is it different from 1) or 2).
Deletions. Yes. Deletions. Changes. Addition.
For example, let's fix the unpopular ugly (unintuitive) image links.
No more .
Use:
{{ pic.gif }} or
{{ fig | pic.gif }} or
{{ fig pic.gif }} or
{{ img pic.gif }} or
pic.gif
Why? Why not?
Here are some "hard" problems solved easily by deletions or
changes:
Paragraph ?!
Heading ?!
---- <-- heading marker, please!?
Paragraph
> We should not be looking at top-level = setext headings, but second-level -
ones, because
> they?re ambiguous with ?thematic breaks?. There are four general ways to
parse this:
- Paragraph, heading, paragraph
- Heading (with 2 lines), paragraph
- Paragraph (with 2 lines), separator, paragraph
- Paragraph (with 4 lines)
A puzzle from the commmarks forum. Now easily solved. Yes.
It's a paragraph (with 2 lines), separator, paragraph. Bingo!
NEW: Setext headings MUST be followed by a blank line.
- ### Big ###
- ## Bigger ##
- # Bigest #
NEW: A heading always MUST start on a new line. Period.
If you're interested, see the Text with Instructions (.text) page [1] or
follow along on Manuscripts News [2] on twitter.
Keep on writing. All the best. Enjoy the summer. Cheers.
[1] https://texti.github.io
[2] https://twitter.com/manuscriptsnews
It seems to me that the first thing to handle is coming up with a means for identifying the version/variant/dialect/fork of "markdown" that a file is coded in. I have been thinking that a variant of #! Would do it, but that's not quite what that is used for (since it confuses format and the application that is expected to process it). (I am looking at #? Myself, but don't have a clear proposal at I still think something like that is called for. Have a way of identifying the format of the text and, ideally, leading to where the rules and definition can be found. Have it in a form that can be ignored, and still be forgiving when there is no such information and a consuming software does the best that can be figured out. - Dennis PS: I am looking at #? myself, for leading format specifying line(s). Don't have a clear description so far, but there's more thinking at <http://nfoware.com/notes/2017/02/n170201.htm>. I will be using this for some different formats that I want to introduce (having little or nothing to do with markdown).> -----Original Message----- > From: Markdown-Discuss [mailto:markdown-discuss- > bounces at six.pairlist.net] On Behalf Of Gerald Bauer > Sent: Tuesday, July 18, 2017 05:49 > To: Discussion related to Markdown. <markdown-discuss at six.pairlist.net> > Subject: Fixing Markdown Series @ Manuscripts News > > Hello, > > First thanks for the great mailing list service. Since I'm just > talking to myself here this will be my last post on markdown list > (never say never ;-) Anyways, they never come back, don't they? > > > If you follow along there are different ways to "fix" markdown: >[ ... ]