> > Since avoiding the problem altogether should never be discounted — Can you > elaborate on why you're stripping the extensions after the fact rather than > just naming source files "foo.pm" => renders to "foo"? (If you want it to > use an HTML template, you could add a `template` meta to the source file). >
I tried this to start with, but it breaks pollen! Since the documentation always talks of relevant extensions, I assumed this use-case is not supported, hence I forget to mention it. To reproduce, create a file "hello.pp" with contents: #lang pollen Hello world! If I run "raco pollen render hello.pp", it explodes: rendering hello.pp rendering: /hello.pp as /hello ->symbol: Can't convert #f to symbol context...: /Applications/Racket v6.4/collects/racket/private/more-scheme.rkt:163:2: select-handler/no-breaks render26 render-from-source-or-output-path loop (submod /Users/agmck/Library/Racket/6.4/pkgs/pollen/pollen/private/command.rkt raco): [running body] /Applications/Racket v6.4/collects/raco/raco.rkt: [running body] /Applications/Racket v6.4/collects/raco/main.rkt: [running body] Renaming the file to hello.pm and adding a custom template meta gives the same result. And even if this were to work, I think I would run into additional problems using poly output files (how to specify an empty poly-tagret). So yeah :D My current solution works, I was just curious if anyone had an alternative way of dealing with this. I could use the template to write all output to a separate file, but that's all I can think of. Cheers! Alexander PS. Enjoyed your racketcon talk and very much looking forward to the rest of beautiful racket. -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
