👍 Awesome! Thank you very much.
--
Leandro Facchinetti
https://www.leafac.com
--
You received this message because you are subscribed to the Google Groups
"Pollen" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to pollenpub+unsubscr...@googlegroups.com.
OK, I just pushed an update with a `--subdir` switch that behaves this way.
> On Mar 7, 2018, at 3:32 AM, 'Leandro Facchinetti' via Pollen
> wrote:
>
> Hi,
>
> Consider the following Pollen project:
>
> ;; a.txt.pp
> #lang pollen
> ◊(current-project-root)
>
> ;; s/b.txt.pp
> #lang poll
> On Mar 7, 2018, at 8:01 AM, 'Leandro Facchinetti' via Pollen
> wrote:
>
> I believe the directory containing ‘pollen.rkt’ is the “real home directory.”
> Is this conception problematic?
Yes. Consider a project structured like this at the top level:
a.html.pm
pollen.rkt
sub/b.html.pm
sub/po
> The idea of `raco pollen render --recursive` is that every directory is being
> treated as its own subproject. Same as if you had done `cd` into each
> directory and `raco pollen render` from there.
That makes sense, but leaves me wishing for an operation intended at rendering
what ‘raco poll
This sounds wrong.
And yet: is it?
`current-project-root` is documented as the "the directory where you launched
raco pollen start". (I'm not saying that pedantically — I often read the Pollen
docs to find out things I've forgotten ;)
The idea of `raco pollen render --recursive` is that eve
Hi,
Consider the following Pollen project:
;; a.txt.pp
#lang pollen
◊(current-project-root)
;; s/b.txt.pp
#lang pollen
◊(current-project-root)
I wish the outputs of ‘current-project-root’ to be consistent, always pointing
to the project root where a ‘pollen.rkt’ might live. When I
