[pollen] ‘raco pollen start’ and ‘raco pollen render --recursive’ inconsistent with respect to ‘current-project-root’

['Leandro Facchinetti' via Pollen]

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 ‘raco pollen 
start’, the development server exhibits that behavior: I visit both 
‘http:///a.txt’ and ‘http:///s/b.txt’ and see the same 
output. But when I ‘raco pollen render --recursive’, the outputs disagree: 
‘s/b.txt’ includes the ‘s/’ directory.

My current workaround is to use ‘define-runtime-path’ in ‘pollen.rkt’ and 
forego ‘current-project-root’. Is there a better solution?

Thanks.

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

Re: [pollen] ‘raco pollen publish’ shouldn’t publish templates

['Leandro Facchinetti' via Pollen]

Fair enough 

> On 2018-03-02, at 16:51, Shrutarshi Basu <s...@basus.me> wrote:
> 
> My solution to this sort of issue is to delegate it to the 
> publish-to-web-server step. I use rsync to push files from the local 
> directory that pollen publishes to locally, and rsync lets you specify files 
> to exclude.
> 
> 
> On March 2, 2018 at 3:47:03 PM, Matthew Butterick (m...@mbtype.com 
> <mailto:m...@mbtype.com>) wrote:
> 
>> I agree. But templates can have any name. ("template.html" is just the 
>> default convention.) So automatic filtering could be finicky.
>> 
>> I think the best policy is to use the `omitted-path?` setting in 
>> pollen/setup. I just failed to do so in this instance ;)
>> 
>> 
>>> On Mar 2, 2018, at 11:42 AM, 'Leandro Facchinetti' via Pollen 
>>> <pollenpub@googlegroups.com <mailto:pollenpub@googlegroups.com>> wrote:
>>> 
>>> For example, https://typographyforlawyers.com/template.html 
>>> <https://typographyforlawyers.com/template.html>
>>> 
>>> Do you agree?
>> 
>> --
>> 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 
>> <mailto:pollenpub+unsubscr...@googlegroups.com>.
>> For more options, visit https://groups.google.com/d/optout 
>> <https://groups.google.com/d/optout>.
> 
> -- 
> 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 
> <mailto:pollenpub+unsubscr...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.


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

[pollen] ‘raco pollen publish’ shouldn’t publish templates

['Leandro Facchinetti' via Pollen]

For example, https://typographyforlawyers.com/template.html 


Do you agree?

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

Re: [pollen] invitations for thoughts about the Pollen / LaTeX nexus

['Leandro Facchinetti' via Pollen]

> 1) There is a small set of recurring problems that arise with LaTeX, that 
> could maybe have common solutions.

Unfortunately, I feel like some of the issues that trouble me the most are out 
of Pollen’s reach. For example, positioning things in particular places on the 
page depends on TeX’s internal understanding of things (‘\textwidth’ and 
friends). And there’s no straightforward way to interact with information at 
this level but to use TeX.

That said, Pollen as it is does solve other pressing issues! For example, the 
arbitrary restriction of 9 arguments for a macro, the lack of named arguments, 
and so forth 

> + a `pollen/latex` dialect that converts LaTeX into X-expressions?

It’s possible to approximate this, and these approximations are useful. But, 
fun story, parsing TeX is undecidable 
.

> + Though I've been reluctant to put self-contained templates into Pollen, I 
> also recognize that a huge number of LaTeX users just rely on those six 
> default templates that it's had since 1979 or whatever. So it would make 
> sense to make it easy to use those templates in Pollen (though maybe that's 
> better put into a separate add-on library, so that my philosophical purity is 
> preserved.**
> 
> [** No. The real reason I've avoided putting readymade templates in Pollen is 
> because I don't want to attract people who really want a turnkey system like 
> Squarespace or WordPress.]

I like this philosophical purity. It’s why I use Pollen. When I want opinions 
and templates, I use Scribble (which comes with the best-looking HTML in the 
market ).

I suppose that, at best, Pollen could be a leaky abstraction—one would still 
need to understand TeX and LaTeX. I’m more interested in replacing the beast 
altogether, and have a PDF rendering engine interacting with Pollen directly. 
In other words, Quad!
-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [pollen] Seeking Advice re: Pollen

['Leandro Facchinetti' via Pollen]

My two cents.

I do something similar to Matthew: ‘.rkt’ in DrRacket and ‘.html.pm’ somewhere 
else (Atom with the language-pollen  
package).
-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [pollen] Dynamically generating a pollen book site for every user

['Leandro Facchinetti' via Pollen]

> 1. How do I connect the dynamically created eBook ( using Json ) with my own 
> Meteor website securely?


Here’s my initial take: JSON → Pollen Markup → LaTeX → PDF → Meteor. From the 
JSON your application generates, you write code that transforms it into Pollen 
Markup. When executed by Pollen, that markup creates a PDF, through LaTeX. You 
then serve this PDF through the Meteor server.

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

Re: [pollen] pollen rock 0.4

['Leandro Facchinetti' via Pollen]

Hi Junsong,

Nice job! I tried it and liked it a lot ☺

Here’s another feature request for you (as if you didn’t have enough
already): keep the scrolling position after refreshing the preview pane.

Best.
-- 
Leandro Facchinetti 
https://www.leafac.com
GPG: 0x5925D0683DF3D583

-- 
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.