When I create a new Pharo 9 image and load the baseline of Microdown, the class comments do not render. However, if I also install the baseline of Pillar, everything is OK. So it seems that some necessary packages of Pillar are igrored by Microdown's baseline.

Because right now this is unclear if we can try transparently the new algorithm to identify inlineblock.

And check if a table works.

In markdown we can write

`smalltalk

1 + 2

`

while in microdown we favor

`language=smalltalk

1 + 2

`

We should write tests for this.

We will have to pay attention to plain text.

so that we can debug some situation.

They are based on the Pillar logic and this is not possible since this is indent first then markup.

I would expect the "Change input syntax" button in PEAR to translate between Pillar and Microdown. But it doesn't do that.
Instead, it deletes the text that was written in the editor and replaces it with a default Pillar or Microdown example.

So in fact, "Change input syntax" does what "Get example" should be doing

To debug

renderComment: aString of: aClassOrPackage 

	| builder |
	builder := MicroDownParser builder.
	aClassOrPackage buildMicroDownUsing: builder withComment: aString.
	self flag: #fixMe.
	"I do not like the asText: the interaction between parser, richtext composer should be 
	more obvious"
	"^ [ MicroDownParser asText: builder contents ] on: MicParsingError, MessageNotUnderstood, SubclassResponsibility  do: [ builder contents  ]"
	
	^ MicroDownParser asText: builder contents

Support table with a simple and more relax setup than github.
A table is not forced to have a header definition.

| aaab | jkhjh |
| --- |
| bar |

or
|aaab|jkhjh|
|---|
|bar|

or
| aaa | bbb |
|ccc |ddd |

or
| aaa | bbb
| cc | ddd

Block-level elements cannot be inserted in a table.

When a table contains a header it is the first row and all rows should have that size else they are cut.

Known limits: how to put a pipe in a table?
No support for |

We should probably raise a MicParsingError.

The following is strange

MicroDownParser parse: '!!note this is like that. Lists cannot be nested in annotated blocks.
But I can be expressed on multiple lines.

1. one
2. Two'

the annotated paragraph does not have children just a large text!

Here are some situations when everything you were writing can be gone:

1. Close Pear window
2. Press "New"
3. Press "Change input syntax"
4. Press "Show example"

It would be nice to show a warning in those cases: "If you leave before saving, your changes will be lost."
This issue is not critical, because in cases 2-4 you can still press Ctrl+Z and restore what you were writing

Related to issue #41
@Ducasse has fixed the baselines today, so now the Microdown can be installed properly in Pharo 9. And class comments are rendered correctly.

Except for the comments that contain math :(
Those ones do not render

asPillar
	
	^ PRMetadata new 
			metadata: (STON fromString: '{', self body, '}'); yourself

should be more robust

To hide markups from user.

• Associate the builder to the parser.
• Example

aBuilder codeBlock: kind withBody: str

instead of

parser codeblockMarkup, String cr, .....

• Package
• Tests
• Baseline
• Traits

asMicroDownUsingBuilder: aBuilder withBody: aString 

Parser inline Microdown : rajouter le paramètre isEvaluated dans les inline blocks et changer le code en conséquence
monospace is not evaluated
reference are not evaluated
figures are only evaluated on caption

the tests are green but only because everything is fucked up.

• Introduce a setting to stop using richtext for comments
• Introduce a comment so that we can stop control exception to be able to script well formness of comment.

Missing a new line before heading: 3

right now

{ "title" : "Pharo by Example" }

has an empty body while

{
"title" : "Pharo by Example"
}

works

Given the line based structure of microdown.
we could accept

{ "title" : "Pharo by Example",
 "title2" : "A cool book"
}

But after all the following is much better.

{ 
"title" : "Pharo by Example",
"title2" : "A cool book"
}

Because this is totally unclear that it is working.

In Pear, we write the Microdown or Pillar text on the left and then Render it into a formatted preview on the right.
I think that the Preview should not be editable because it's not possible to save the changes or to update the code based on the changes in the Preview.

Steps to reproduce:

1. Create a new Pharo 9 image
2. Open Tools > Pear
3. Press "Change input syntax"
4. Press "New". You will get an empty editor
5. Type some Microdown text
6. Press "Render". You should see the correctly rendered output on the right
7. Press "Save". And BOOM!

It does not have a PRassociated class?
uh?

There is no asPillar for math environment

In addition the parameters do not seem to be well treated in codeblock and other.
May be we lost code of laurine/

All the examples are broken as well as PRCodeblockStylerExtension class examplePillar1.

asPillar

^ PRCommentedLine new
		text: text ;
		yourself

When writing text in the editor, it is really handy to have keyboard shortcuts for the basic operations such as "Save" and "Render". However, I think that other options should be supplied with shortcuts as well ("New", "Open" etc.)

Why is it important:

1. It saves time
2. It makes sure that you don't lose your thought when you write
3. It encourages to Render and Save often

The standard editor shortcuts Ctrl+S, Ctrl+N, Ctrl+O, Ctrl+T (Cmd+S, Cmd+N, Cmd+O, Cmd+T) are already used in Pharo.
I don't know if it's possible to redefine them for the case when PEAR window is in focus.
If yes - that would be great!

I'm really glad to see microdown as a bridge between (a variant of a) Markdown syntax in the surface and the Pillar machinery in the back end, as it could lower/end the Grafoscopio reliance on external dependencies (ie. Pandoc, Lunamark) for markup conversions between Markdown and HTML/LaTeX/PDF. Thanks for microdown.

Several Markdown variants have adopted YAML metadata block (gfm shows them as tables, Zettlr, Pandoc, Jeykill and other static site generators use it to define even operations and properties of the exported documents once they become LaTeX, HTML and so on). Such blocks are at the beginning of the document containing between --- the document metadata, like this:

---
name: example
context:
  - type: feature request.
  - url: https://github.com/pillar-markup/MicroDown/issues/57
--- 

Can YAML metadata blocks support be added to microdown (or as a plugin), so YAML inside a microdown text can be converted to (Ordered) dictionaries in Pharo?

Thanks again.

Backslashes \ are very important in math environments, but Microdown removes them.
So they have to be escaped, which is very annoying and breaks the compatibility of Microdown math with standard LaTeX math.

For example, in LaTeX I would write

$ f(a) = \frac{1}{2\pi i} \oint_{\gamma} \frac{f(z)}{z - a} dz $

and get this:

But in Microdown it doesn't work:

What I have to do then is escape all backslashes. Like this:

$ f(a) = \\frac{1}{2\\pi i} \\oint_{\\gamma} \\frac{f(z)}{z - a} dz $

Then everything is fine:

But it would be great if backslashes were not captured in math environments.

Here are the lines that can be added:

Here are several examples:

#### Example 1
Code: `$V_i = C_0 - C_3$`

$V_i = C_0 - C_3$

#### Example 2
Code: `$a^2 + b^2 = c^2$`

$a^2 + b^2 = c^2$

#### Example 3
Code: `$\\sin(x) = \\sum_{n=0}^{\\infty} \\frac{(-1)^{n}x^{2n+1}}{(2n+1)!}$`

$\\sin(x) = \\sum_{n=0}^{\\infty} \\frac{(-1)^{n}x^{2n+1}}{(2n+1)!}$

#### Example 4
Code: `$f(a) = \\frac{1}{2\\pi i} \\oint_{\\gamma} \\frac{f(z)}{z - a} dz$`

$f(a) = \\frac{1}{2\\pi i} \\oint_{\\gamma} \\frac{f(z)}{z - a} dz$

One way to reproduce the error is using a vpn + asking to see the syntax help.

`$$` produces a DNU

Le block <?cite|a=1&b=17&c
Hello

Pharo
?>
ne doit pas produire une citation mais un PREnvironment avec cite comme nom