Dmitri Zagidulin writes:
> On Friday, April 10, 2015, Damien Cassou wrote:
>> website is clearer. Something you could do however is to add links for
>> each project in the todo: these links go target mailing list discussions
>> (or a github tracker or both if we go that
>>
> Sure! Happy to add
On Friday, April 10, 2015, Damien Cassou wrote:
> website is clearer. Something you could do however is to add links for
> each project in the todo: these links go target mailing list discussions
> (or a github tracker or both if we go that
>
Sure! Happy to add links.
Just to double-check, thou
>
> ${inputFile:myFile.pillar}$
> on your file to include your myFile.pillar.
>
Cool! I can stop using my Ruby-based preprocessing soon :). (Especially
when the variant with the scripts will be added.)
> How do you feel about also having a GitHub repo for the Pillar project?
> That way, we could
On Thu, Apr 9, 2015 at 11:02 AM, Damien Cassou
wrote:
>
> > So, any chance to make them multi-line capable?
>
> that's a feature I would also like to see. Would you please add this to
> the list of feature requests?
> http://www.smalltalkhub.com/#!/~Pier/Pillar. I've just added
> DmitriZagidulin t
Dmitri Zagidulin writes:
> Ahh, that's very cool!
>
> Though this is way off-topic from internal links (but I'm not sure where to
> bring this up, if there's a pillar repo somewhere) -- is there any way you
> can implement multi-line annotations? (and multi-line list items, for that
> matter). U
Ahh, that's very cool!
Though this is way off-topic from internal links (but I'm not sure where to
bring this up, if there's a pillar repo somewhere) -- is there any way you
can implement multi-line annotations? (and multi-line list items, for that
matter). Using either an open/close syntax, or Ma
Hi.
With Damien we're working on the creation of Annotation and Transformers.
Now you can use this Annotation's tag :
${inputFile:myFile.pillar}$
on your file to include your myFile.pillar.
That still can change a bit, i'm working on it and i still need to do the
tests.
On 7 April 2015 at 18:40,
Thanks, Cyril!
We bumped into the internal link (with label) limitation, too, in Updated
Pharo by Example (
https://github.com/SquareBracketAssociates/UpdatedPharoByExample/issues/10#issuecomment-89044176
).
So, +1 interest to that feature, here :)
On Tue, Apr 7, 2015 at 11:03 AM, Cyril Ferli
Ok, keep me posted.
Thanks,
Peter
On Tue, Apr 7, 2015 at 5:03 PM, Cyril Ferlicot
wrote:
> Hi !
> Inter-File link are on the TODO list of pillar. Currently you can't.
> I'm working on Pillar now, if i add inter-file link i'll say it to you !
>
> On 7 April 2015 at 16:45, Peter Uhnák wrote:
>
>>
Hi !
Inter-File link are on the TODO list of pillar. Currently you can't.
I'm working on Pillar now, if i add inter-file link i'll say it to you !
On 7 April 2015 at 16:45, Peter Uhnák wrote:
> Hi,
>
> how does one add an internal link?
> I have chapter 'Framework' (and file 'Framework/Framework
Hi,
how does one add an internal link?
I have chapter 'Framework' (and file 'Framework/Framework.pillar') and
'Palette' (and file 'Palette/Palette.pillar')
Can I in Framework.pillar write something like *Palette/Palette* to create
a link?
Currently it fails at
*** Warning: PRReferenceNotFound: C
11 matches
Mail list logo
