You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 12, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 12, 2026. It is now read-only.
If there’s only one found, just print PDF with the name of this file: index.pdf, not presentation.pdf like it does right now. You don’t expect presentation name because you don’t use it anywhere.
If there are multiple files, list all of them and ask which one to print, just like it does for the themes.
Why such a hard workflow? Isn't it easier to count all /*.(htm|html) files of the presentation entry points? Then calling shower pdf will just turn all the entry points into PDF file.
When I run shower pdf I want to export a single file, not every HTML file available. There might be a demo file or something else. To be able to print exactly what I need, I’d love to see something like:
$ ls
$ foo.html bar.html
$ shower pdf foo.html
>> foo.pdf
$ shower pdf
> foo.html
> bar.html ←
>> bar.pdf
shower pdf behavior would be similar to npm run one, where it lists all available options instead of running all of them.
Activity
mrdimidium commentedon May 2, 2019
Hey. Sorry for the long answer.
Why such a hard workflow? Isn't it easier to count all
/*.(htm|html)files of the presentation entry points? Then callingshower pdfwill just turn all the entry points into PDF file.pepelsbey commentedon May 2, 2019
When I run
shower pdfI want to export a single file, not every HTML file available. There might be a demo file or something else. To be able to print exactly what I need, I’d love to see something like:shower pdfbehavior would be similar tonpm runone, where it lists all available options instead of running all of them.mrdimidium commentedon May 2, 2019
Sounds good, we'll do it