ok people I think I made pillar angry :D I dont why, maybe I said something I should not have said, maybe I pushed her too much , maybe I smell too bad but since yesterday she compiles but refuses to cooperate with me.
In detail each time I try to use pillar syntax lets say "!! Finding classes" instead of seeing the syntax and compile to something like "1.2 Finding classes" it compiles it as it is "!! Finding classes" , it does the same thing with other pillar syntax too. I tried to redownload the repo , and reinstall pier and recompile from scratch again it does the same things. You can replicate this by cloning the UpdatedPharoByExample github repo and just go to PharoTour.pier and add "!! Something something" and compile. The problem is evident in both the pdfs and hmtl outputs. Please help me make pillar friendly again, tell her I apologize and I lover her very much :) On Sat, May 10, 2014 at 7:09 PM, kilon alios <[email protected]> wrote: > Thanks Damien and Yuriy > > > On Sat, May 10, 2014 at 6:51 PM, Yuriy Tymchuk <[email protected]>wrote: > >> >> On 10 May 2014, at 17:01, kilon alios <[email protected]> wrote: >> >> I found a bug in Pillar syntax >> >> when I type 3 + 4 , it seems like it takes + as part of the pillar >> syntax and uses latex syntax and when it tries to generate the pdf it fails >> so I am forced now to type it as raw text like this : {{{3+4}}} >> >> >> It’s not a bug, it’s a feature :). I’d suggest you to use something like >> ==inline code== for wrapping of ‘’italic’'. >> >> >> also I would like the ability to have a dark background for text like we >> do with smalltalk syntax . >> >> >> I don’t really understand what you need. If you need to style the result, >> it should be done outside of pillar. >> >> >> >> Pharo Tour chapters proceeds well, I compile to both latex html and pdf , >> I see no problems so far with my text, I copy my text directly from the >> latex files of the original PBE in github. >> >> >> I also improved the Readme. >> >> >> On Thu, May 8, 2014 at 9:16 AM, stepharo <[email protected]> wrote: >> >>> >>> >>> I also added Chapter 1 - Quick Tour in Pharo. Just the first part , >>> the chapter is of course still a WIP. >>> >>> I am not so sure what you mean about automated tests, are they for the >>> example code ? >>> >>> >>> >>> if you see in the tex when we have example we also have a tag that >>> indicates that the code can be extracted >>> and run. I do not remember but oscar did a script and we where able to >>> automatically verify that all the simple examples were correctly working >>> with a version of Pharo. >>> >>> Now in Pillar we should introduce the notion of tag to support at the >>> word level. >>> - index >>> - comment >>> - citation >>> >>> >>> >>> I am all for automation. >>> >>> >>> On Mon, May 5, 2014 at 11:08 PM, stepharo <[email protected]> wrote: >>> >>>> This is really cool that people want to update the Pharo by Example >>>> book. >>>> This is a really an important task and it will have a real impact. >>>> You can also reduce the number of screenshots or point related to the >>>> interaction. >>>> >>>> What would be good is to make the automated tests working again because >>>> we could spot >>>> if we got some regressions. >>>> >>>> Stef >>>> >>>> >>>> How I can help improve Pharo by Example , add chapters and update >>>>> current ones for Pharo 3 ? >>>>> >>>>> What is the process ? >>>>> >>>> >>>> >>>> >>> >>> >> >> >
