Re: [pollen] Source files in multiple directories and generating an index

2019-02-19 Thread Evžen Wybitul
Darn, you're right! I'd swear I ran `raco pkg update --all`. There must've 
been an error I haven't noticed which prevented pollen from updating (ah, 
it's getting late here in Europe). I'm really sorry for bothering you. 
Everything works fine now :-) You're the best!

Dne středa 20. února 2019 1:03:12 UTC+1 Matthew Butterick napsal(a):
>
> (FWIW I cannot reproduce your bug with 1.5.2028.835)
>
>
> On Feb 19, 2019, at 4:02 PM, Matthew Butterick  > wrote:
>
> The revision with the bugfix is 1.5.2028.835.
>
>
> On Feb 19, 2019, at 4:01 PM, Evžen Wybitul  > wrote:
>
> It says 1.5.1987.839
>
> Dne středa 20. února 2019 1:00:33 UTC+1 Matthew Butterick napsal(a):
>>
>> What is your `raco pollen version`?
>>
>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.


Re: [pollen] Source files in multiple directories and generating an index

2019-02-19 Thread Matthew Butterick
(FWIW I cannot reproduce your bug with 1.5.2028.835)


> On Feb 19, 2019, at 4:02 PM, Matthew Butterick  wrote:
> 
> The revision with the bugfix is 1.5.2028.835.
> 
> 
>> On Feb 19, 2019, at 4:01 PM, Evžen Wybitul > > wrote:
>> 
>> It says 1.5.1987.839
>> 
>> Dne středa 20. února 2019 1:00:33 UTC+1 Matthew Butterick napsal(a):
>> What is your `raco pollen version`?
> 

-- 
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.
For more options, visit https://groups.google.com/d/optout.


Re: [pollen] Source files in multiple directories and generating an index

2019-02-19 Thread Evžen Wybitul
Good idea, I'm now converting them to relative path names. I'm still having 
trouble with getting custom templates to work, though; I have a file 
*analysis/document.html.pm 
*and I'd like it to be render with a *special-template.html*, which is in 
the root directory* (*outside of the *anaylsis *folder*). *I can't find any 
way to do that.

I tried to set the template file using define-metas, but neither of these 
worked: *special-template.html, /**special-template.html, 
/full/system/path/to/file/**special-template.html.*

Got any more tips?

Dne pondělí 21. ledna 2019 17:12:28 UTC+1 Matthew Butterick napsal(a):
>
>
>
> On Jan 20, 2019, at 11:33 PM, Evžen Wybitul  > wrote:
>
> And it works, partially. However, when I call `(next here)` on order to do 
> page navigation, the value for file1 is `analysis/file2.html`, but I'd need 
> it to be only `file2.html`. Of course, I could just strip the `[...]/` part 
> programatically, but that feels really hack-ish. Especially if there's a 
> better way.
>
>
> In essence, you are tracking absolute path names in the pagetree, but you 
> want them to behave like relative path names. You can either 1) convert 
> them to relative path names, or 2) use them as absolute URLs (that is, 
> prefix them with "/") though that assumes you only need the links to work 
> when served via HTTP.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.


Re: [pollen] Source files in multiple directories and generating an index

2019-01-21 Thread Matthew Butterick


> On Jan 20, 2019, at 11:33 PM, Evžen Wybitul  wrote:
> 
> And it works, partially. However, when I call `(next here)` on order to do 
> page navigation, the value for file1 is `analysis/file2.html`, but I'd need 
> it to be only `file2.html`. Of course, I could just strip the `[...]/` part 
> programatically, but that feels really hack-ish. Especially if there's a 
> better way.

In essence, you are tracking absolute path names in the pagetree, but you want 
them to behave like relative path names. You can either 1) convert them to 
relative path names, or 2) use them as absolute URLs (that is, prefix them with 
"/") though that assumes you only need the links to work when served via HTTP.

-- 
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.
For more options, visit https://groups.google.com/d/optout.


Re: [pollen] Source files in multiple directories and generating an index

2019-01-20 Thread Matthew Butterick

> On Jan 20, 2019, at 12:03 PM, Evžen Wybitul  wrote:
> 
> 1. I can't find out how to keep the "notes" from different subjects in 
> different folders. The problem is I'm unable to dynamically build the 
> "master-index" of such files. 

What have you tried that didn't work? It seems straightforward to put code 
inside "master-index.html.pm" that reads the contents of adjacent directories 
and makes links.



> 2. I'd like to have the output files in one folder, and not side by side with 
> the source files (solvable by `raco pollen publish`, but that's an extra 
> command I have to manually run).


Which, in turn, can be solved by putting your build commands into a makefile. 
This feature has been requested before. But it's a lot more annoying to 
implement than it seems. Once the two directories are separate, there's a whole 
new set of error conditions that can arise.


> Forgot this: I'd also like to use only one template and css file for all of 
> the files. 


If you put your template & css in the root directory of the project, the source 
files in the subdirectories should find it.

-- 
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.
For more options, visit https://groups.google.com/d/optout.