> On Feb 28, 2019, at 6:42 AM, Brendan Stromberger
> wrote:
>
> I can't seem to get next/previous navigation working. When I use `◊(previous
> here)` and `◊(next here)`
> for my nav links, they evaluate to blank strings. `◊|here|` correctly
> evaluates (as far as I can tell) to the current do
Alright, I'm making progress, but not quite there yet.
In my template, I have `◊(define here (path->pagenode (->output-path
(hash-ref metas 'here-path`
This renders out to a pagenode that looks something like
"body/3_the_trigrams.html"
When I send this pagenode into `next` or `previous`, i
> On Feb 28, 2019, at 3:17 PM, Brendan Stromberger
> wrote:
>
> In my template, I have `◊(define here (path->pagenode (->output-path
> (hash-ref metas 'here-path`
>
> This renders out to a pagenode that looks something like
> "body/3_the_trigrams.html"
>
> When I send this pagenode into
> On Feb 28, 2019, at 4:28 PM, Matthew Butterick wrote:
>
> But I would put the code inside a function in "pollen.rkt". In that case you
> can pass `metas` as an argument, or use the `current-metas` parameter.
(Of course in that case the `require` could go at the top of the file with the
oth
Thanks for your help. Here are some output values for the functions
defined...
root: /Users/vro/Desktop/dev/richmond/
here-path: /Users/vro/Desktop/dev/richmond/body/3_the_trigrams.poly.pm
here-path-relative: body/3_the_trigrams.poly.pm
here-path-pagenode: body/3_the_trigrams.poly.pm
next-pat
Whoops, the inconsistency with the paths and the extensions was my bad, my
ptree file was borked. :)
On Friday, March 1, 2019 at 2:08:52 PM UTC-5, Brendan Stromberger wrote:
>
> Thanks for your help. Here are some output values for the functions
> defined...
>
> root: /Users/vro/Desktop/dev/ric
> On Mar 1, 2019, at 11:08 AM, Brendan Stromberger
> wrote:
>
> build-path: contract violation
> expected: (or/c path-for-some-system? path-string? 'up 'same)
> given: 'body/2_understanding_the_lines.poly.pm
> argument position: 2nd
> other arguments...:
>#
My error, the last line n
Alright, I'm up and running :)
Thanks!
On Friday, March 1, 2019 at 2:13:46 PM UTC-5, Matthew Butterick wrote:
>
>
> On Mar 1, 2019, at 11:08 AM, Brendan Stromberger > wrote:
>
> build-path: contract violation
> expected: (or/c path-for-some-system? path-string? 'up 'same)
> given: 'body/2_und
