https://github.com/msprev/dot-panzer
my panzer support directory
https://github.com/msprev/dot-panzer
Last synced: about 1 year ago
JSON representation
my panzer support directory
- Host: GitHub
- URL: https://github.com/msprev/dot-panzer
- Owner: msprev
- Created: 2014-11-01T16:19:43.000Z (over 11 years ago)
- Default Branch: master
- Last Pushed: 2019-02-12T13:22:16.000Z (over 7 years ago)
- Last Synced: 2025-04-22T20:14:57.615Z (about 1 year ago)
- Language: Python
- Homepage:
- Size: 274 KB
- Stars: 11
- Watchers: 3
- Forks: 3
- Open Issues: 1
-
Metadata Files:
- Readme: readme.md
Awesome Lists containing this project
README
---
Development has ceased on panzer. Over the years, pandoc has gained powerful new functionality (e.g. the `--metadata-file` option and Lua filters) that means that 90% of what can be done with panzer can be done with pandoc and some simple wrapper scripts. I no longer use panzer in my own workflow for this reason.
If you would like to take over development of panzer, let me know.
---
My personal `.panzer` files.
Install to `$HOME/.panzer/` to use them.
Note this useful experience from [fredcallaway](https://github.com/fredcallaway) described here: https://github.com/msprev/dot-panzer/issues/6
> I struggled for a long time trying to generate a pdf with panzer foo.md -o foo.pdf before realizing that the command should be panzer foo.md -o foo.tex. It might be worth including that information somewhere for other wandering souls :)
There are 2 ways to generate a pdf in pandoc/panzer:
1. Quick-and-dirty by passing .pdf as the output extension to pandoc/panzer
2. Writing .tex and using a postflight script to compile to pdf
My .panzer files use (2).