Re: [pollen] How to access current output type from `pollen.rkt'?

2016-10-20 Thread lfacchi2
As usual, thank you very much. Your quick, precise and complete answers are part of what makes using Pollen a joy. I think adding assignments to current-poly-target in all source files would pollute them. This is redundant information already stated in the file name. That is why I regarded it

Re: [pollen] How to access current output type from `pollen.rkt'?

2016-10-20 Thread Matthew Butterick
On Oct 20, 2016, at 8:33 AM, lfacc...@jhu.edu wrote: > Use (current-poly-target). Notice that the files have extensions such as > .html.pm and .atom.pm, and not .poly.pm. This is no accident, since each file > only generates one output type. Thus, (current-poly-target) always answers > with

[pollen] Collecting a wish list for a pollen editor

2016-10-20 Thread Li Junsong
Hi list, I am collecting a wish list for a pollen editor. I am wondering on which OS are people here using pollen? What kind of editing features you desire most when you edit your pollen source file in your favorite editor? I always wish my editor could tell me whether a tag is defined and

[pollen] How to access current output type from `pollen.rkt'?

2016-10-20 Thread lfacchi2
*PRE-CONDITIONS* The book contains the files: *index.html.pm* #lang pollen ◊foo{Bar} *feed.atom.pm* #lang pollen ◊foo{Baz} *pollen.rkt* #lang racket (define (foo . elements) ...) *USE CASE* The foo function needs to behave differently when generating different output