StéphaneDucasse

``` /pillar/build/pillar-db build pdf FirstConfiguration.m ``` makes pillar bark! It should not

pillar build pdf -m AFILE ignores AFILE

1

Right now `pillar build pdf -m` does nothing more compared to `pillar build pdf` It just works if there is one single file and we cannot specify that file.

At least we tested with two slides and they cannot be handled because we have a problem in ``` CollectionIsEmpty: a Stack() is empty Stack(Collection)>>errorEmptyCollection Stack(Collection)>>emptyCheck Stack(LinkedList)>>removeFirst Stack>>pop PRSlideTransformer(PRNodeTransformer)>>replace: PRSlideTransformer(PRNodeTransformer)>>delete...

Right now when we compile a book containing multiple files with md or pillar as extension, we only filter the readme ones. It would be good that the user can...

The testAnnotationAsPillar hardcodes the syntax for annotation and it would be better to use the builder. ``` testAnnotationAsPillar | res | res := self splitter pillarFrom: 'abc{!cite|a=2&b=5!}def'. self assert: res...

The API of PRInputDocument is not that good

1

``` includedPillarAST := ((PRInputDocument inputClassForFile: includedFile) new "project: aProject;" file: includedFile contents; yourself) parsedDocument. ``` file: should expect a file reference and the parseDocument should do what it should. Then...

- missing io in OSWinSubProcess

When releasing/tagging Pillar

1

We should not forget to freeze microdown or we should not depend on the microdownDev baseline. ``` BaselineOfPillarApp ... "Microdown - we want it in App." spec baseline: 'MicrodownDev' with:...

``` caption ^ caption ifNil: [ caption := self parameters at: 'caption' ifPresent: [ :string | (PRDocument parser parse: string) children first ] ifAbsent: [ PRParagraph with: (PRText content: '')...

So that the PRParser is separated from the rest