Hi
Is there anybody maintaining Pillar? I did wget https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh chmod +x download.sh ./download.sh ./pillar archetype book ogrammingArchetype make pdf git submodule update --init --recursive mkdir -p ./build ln -fs ../support ./build support/latex/sbabook/gitinfo2.sh > build/gitHeadLocal.gin /bin/sh: support/latex/sbabook/gitinfo2.sh: Permission denied make: *** [build/gitHeadLocal.gin] Error 126 I have no idea how to fix it. in the past I removed this git version script because it was going in my way. Stef |
- chmod +x support/latex/sbabook/gitinfo2.sh Now I have no idea where I should add this command. Then how can I modify the makefile and version it in my version of the book ? Should I just add Makefile to my git repo? Stef Le 9/10/16 à 19:42, stepharo a écrit : > Hi > > Is there anybody maintaining Pillar? > > > I did > > wget > https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh > > chmod +x download.sh > > ./download.sh > > ./pillar archetype book > > ogrammingArchetype make pdf > git submodule update --init --recursive > mkdir -p ./build > ln -fs ../support ./build > support/latex/sbabook/gitinfo2.sh > build/gitHeadLocal.gin > /bin/sh: support/latex/sbabook/gitinfo2.sh: Permission denied > make: *** [build/gitHeadLocal.gin] Error 126 > > > I have no idea how to fix it. > > in the past I removed this git version script because it was going in > my way. > > Stef > > > |
In reply to this post by stepharo
Are the files in Chapters automatically added to the pillar.conf?
Because the pillar.conf is just { "title":"Book title", "newLine":#unix, "configurations": { "LaTeX" : { "outputType":#'latex:sbabook', "separateOutputFiles":true }, "HTML" : { "outputType":#html, "separateOutputFiles":true } } } Does it mean that all the files should be always compiling? Stef Le 9/10/16 à 19:42, stepharo a écrit : > Hi > > Is there anybody maintaining Pillar? > > > I did > > wget > https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh > > chmod +x download.sh > > ./download.sh > > ./pillar archetype book > > ogrammingArchetype make pdf > git submodule update --init --recursive > mkdir -p ./build > ln -fs ../support ./build > support/latex/sbabook/gitinfo2.sh > build/gitHeadLocal.gin > /bin/sh: support/latex/sbabook/gitinfo2.sh: Permission denied > make: *** [build/gitHeadLocal.gin] Error 126 > > > I have no idea how to fix it. > > in the past I removed this git version script because it was going in > my way. > > Stef > > > |
In reply to this post by stepharo
I tried to add a title to a book
{ "title":"Learning Programming with Pharo", "newLine":#unix, "configurations": { "LaTeX" : { "outputType":#'latex:sbabook', "separateOutputFiles":true }, "HTML" : { "outputType":#html, "separateOutputFiles":true } } } did not work :( { "title":"Learning Programming with Pharo" } !!Compilation ${inputFile:Chapters/Chapter1/chapter1.pillar}$ !!Edition and Templates ${inputFile:Chapters/Chapter2/chapter2.pillar}$ +>figures/pharo.png|width=30+ +>figures/rmod.png|width=30+ did not work :( No idea how to debug i t sadly. Stef Le 9/10/16 à 19:42, stepharo a écrit : > Hi > > Is there anybody maintaining Pillar? > > > I did > > wget > https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh > > chmod +x download.sh > > ./download.sh > > ./pillar archetype book > > ogrammingArchetype make pdf > git submodule update --init --recursive > mkdir -p ./build > ln -fs ../support ./build > support/latex/sbabook/gitinfo2.sh > build/gitHeadLocal.gin > /bin/sh: support/latex/sbabook/gitinfo2.sh: Permission denied > make: *** [build/gitHeadLocal.gin] Error 126 > > > I have no idea how to fix it. > > in the past I removed this git version script because it was going in > my way. > > Stef > > > |
Hi Stef,
I started from the Pharo image and now we have an editor that is working reasonably well inside Pharo. I will send more details shortly. This means that I do not have to edit the book somewhere else, and this also means that I can run the generation from inside Pharo, too. So, the next step is to trigger the visitors to generate the book from within Pharo without relying on the command line. If we can manage that, my guess is that the command line related logic will become simpler and more debuggable. Cheers, Doru > On Oct 9, 2016, at 8:03 PM, stepharo <[hidden email]> wrote: > > I tried to add a title to a book > > { > "title":"Learning Programming with Pharo", > "newLine":#unix, > "configurations": { > "LaTeX" : { > "outputType":#'latex:sbabook', > "separateOutputFiles":true > }, > "HTML" : { > "outputType":#html, > "separateOutputFiles":true > } > } > } > > did not work :( > > { > "title":"Learning Programming with Pharo" > } > > !!Compilation > > ${inputFile:Chapters/Chapter1/chapter1.pillar}$ > > !!Edition and Templates > > ${inputFile:Chapters/Chapter2/chapter2.pillar}$ > > +>figures/pharo.png|width=30+ > +>figures/rmod.png|width=30+ > > did not work :( > > No idea how to debug i t sadly. > > Stef > > > Le 9/10/16 à 19:42, stepharo a écrit : >> Hi >> >> Is there anybody maintaining Pillar? >> >> >> I did >> >> wget https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh >> >> chmod +x download.sh >> >> ./download.sh >> >> ./pillar archetype book >> >> ogrammingArchetype make pdf >> git submodule update --init --recursive >> mkdir -p ./build >> ln -fs ../support ./build >> support/latex/sbabook/gitinfo2.sh > build/gitHeadLocal.gin >> /bin/sh: support/latex/sbabook/gitinfo2.sh: Permission denied >> make: *** [build/gitHeadLocal.gin] Error 126 >> >> >> I have no idea how to fix it. >> >> in the past I removed this git version script because it was going in my way. >> >> Stef >> >> >> > > -- www.tudorgirba.com www.feenk.com "Problem solving efficiency grows with the abstractness level of problem understanding." |
In reply to this post by stepharo
On 9 October 2016 at 19:47, stepharo <[hidden email]> wrote:
That should be versioned as part of sbabook. On my machine when I check it out it's executable, and apparently it's harder to make git ignore file modes than to have it follow them, so I don't know what's wrong. |
In reply to this post by Tudor Girba-2
Hi doru
> Hi Stef, > > I started from the Pharo image and now we have an editor that is working reasonably well inside Pharo. I will send more details shortly. Cool > This means that I do not have to edit the book somewhere else, and this also means that I can run the generation from inside Pharo, too. Nice. > So, the next step is to trigger the visitors to generate the book from within Pharo without relying on the command line. If we can manage that, I think that we should extract the commandline code into a separated object. I wanted to do that but I decided that I'm not allowed to start something new now. I wanted to generated also all the magritte black magic accessors so that we do not rely on DNU. > my guess is that the command line related logic will become simpler and more debuggable. I wanted to replace some unix commands by some pharo code snippet (because I can debug FileReference) but same reason as above (finish first three tasks before starting a new one). Stef > > Cheers, > Doru > > > >> On Oct 9, 2016, at 8:03 PM, stepharo <[hidden email]> wrote: >> >> I tried to add a title to a book >> >> { >> "title":"Learning Programming with Pharo", >> "newLine":#unix, >> "configurations": { >> "LaTeX" : { >> "outputType":#'latex:sbabook', >> "separateOutputFiles":true >> }, >> "HTML" : { >> "outputType":#html, >> "separateOutputFiles":true >> } >> } >> } >> >> did not work :( >> >> { >> "title":"Learning Programming with Pharo" >> } >> >> !!Compilation >> >> ${inputFile:Chapters/Chapter1/chapter1.pillar}$ >> >> !!Edition and Templates >> >> ${inputFile:Chapters/Chapter2/chapter2.pillar}$ >> >> +>figures/pharo.png|width=30+ >> +>figures/rmod.png|width=30+ >> >> did not work :( >> >> No idea how to debug i t sadly. >> >> Stef >> >> >> Le 9/10/16 à 19:42, stepharo a écrit : >>> Hi >>> >>> Is there anybody maintaining Pillar? >>> >>> >>> I did >>> >>> wget https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh >>> >>> chmod +x download.sh >>> >>> ./download.sh >>> >>> ./pillar archetype book >>> >>> ogrammingArchetype make pdf >>> git submodule update --init --recursive >>> mkdir -p ./build >>> ln -fs ../support ./build >>> support/latex/sbabook/gitinfo2.sh > build/gitHeadLocal.gin >>> /bin/sh: support/latex/sbabook/gitinfo2.sh: Permission denied >>> make: *** [build/gitHeadLocal.gin] Error 126 >>> >>> >>> I have no idea how to fix it. >>> >>> in the past I removed this git version script because it was going in my way. >>> >>> Stef >>> >>> >>> >> > -- > www.tudorgirba.com > www.feenk.com > > "Problem solving efficiency grows with the abstractness level of problem understanding." > > > > > > |
In reply to this post by stepharo
On 9 October 2016 at 19:49, stepharo <[hidden email]> wrote:
No, they don't have to be in it. The main file includes them.
Yes, only the whole-book compilation works for now. Per-chapter compilation works in EnterprisePharo but it's done in the makefile. A proper solution would be to replace all the ${includeFile:foo.pillar}$ directives with something more semantic that does not lose track of which file was included. |
In reply to this post by stepharo
On 9 October 2016 at 20:03, stepharo <[hidden email]> wrote:
I think I tried with { "metadata": { "title": "bleb" } } in the book.pillar and that worked. No clue why the one from the conf is not inherited anymore. |
In reply to this post by Damien Pollet-2
Le 9/10/16 à 21:23, Damien Pollet a
écrit :
no idea. I did a clean install. So I imagine that it should break on other machines too. |
In reply to this post by Damien Pollet-2
Ok thanks! I will try tomorrow.
Stef Le 9/10/16 à 21:29, Damien Pollet a
écrit :
|
In reply to this post by stepharo
On 9 October 2016 at 21:52, stepharo <[hidden email]> wrote: I did a clean install. So I imagine that it should break on other machines too. Might be that pillar archetype doesn't do a git clone but some kind of archive extraction… I know github and zip files have limitations with that |
On 9 October 2016 at 21:59, Damien Pollet <[hidden email]> wrote: Might be that pillar archetype doesn't do a git clone but some kind of archive extraction wait no… sbabook is a submodule, so it's like git clone :| |
Free forum by Nabble | Edit this page |