Hi Doru, This happens with the following files:
https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSuccessfulBuild/artifact/Lint/Lint.pier https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSuccessfulBuild/artifact/ParseTreeRewriter/ParseTreeRewriter.pier https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSuccessfulBuild/artifact/RewriteTool/RewriteTool.pier https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSuccessfulBuild/artifact/MigratedToOtherPlaces/Fuel/Fuel.pillar https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSuccessfulBuild/artifact/MigratedToOtherPlaces/Zinc/Zinc.pier Hernán 2015-03-22 10:05 GMT-03:00 Tudor Girba <[email protected]>: > Could you send me the file you are using? Given that the parser is just an > approximate one, it can be that your specific constructs are not supported. > > Cheers, > Doru > > On Fri, Mar 20, 2015 at 8:59 PM, Hernán Morales Durand < > [email protected]> wrote: > >> Ok, alternatively, is someone generating Pillar chapters in Windows? >> >> My problem is GT-InspectorExtensions-Pillar highlights the syntax but not >> properly (see attachment). Could I be using a wrong syntax? >> >> I also figured out a command line to execute pdflatex passing a modified >> PFTE.tex, but latex errors are cryptic (and I don't want to follow there). >> >> Hernán >> >> >> >> >> 2015-03-17 17:57 GMT-03:00 Hernán Morales Durand < >> [email protected]>: >> >> Is this working? >>> How to preview a .pier file? >>> >>> https://github.com/pillar-markup/language-pillar >>> >>> Cheers, >>> >>> Hernán >>> >>> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >
