HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Wandmalfarbe
pandoc-latex-template
Shell2019–2025
Wandmalfarbe / pandoc-latex-template

pandoc-latex-template

A pandoc LaTeX template to convert markdown files to PDF or LaTeX.

Productivity
Explore on GitHubRead Hacker News discussions
10Distinct people
14Mentions
0Explicit recommenders
7.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A pandoc LaTeX template to convert markdown files to PDF or LaTeX.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year14 dated mentions

Observed mentions: 2019-04-06 08:13:17 UTC to 2025-11-05 13:45:48 UTC.

01232019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC312
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC202
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC211
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC312
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC211

What Hacker News says

14 sources
starkparker·Feb 2, 2024
You can inline LaTeX chapter/section break commands even when processing Markdown, and in several ways (dropping \newpage directly in the content before chapters, using header templates, as YAML metadata in the Markdown file, even on the command line). Google has many examples; one's here using a header file: https://medium.com/@sydasif78/book-creation-with-pandoc-and-... More are here, including an example using the header-includes YAML metadata param: https://github.com/Wandmalfarbe/pandoc-latex-template/issues...
In Pandoc
eslaught·Dec 26, 2021
There's really no reason you need to switch. You can put raw LaTeX directly into Pandoc Markdown documents; it'll be ignored in non-LaTeX backends, and in LaTeX it'll just be reproduced verbatim. If you need to tweak the template that Pandoc puts "around" the Markdown content, you can do that too (and then centralize your changes so you don't need to do it over and over again). Eisvogel is an example of a project that does this [1]. I think this is really the best of both worlds, because you can produce documents that (fairly) easily generate print books via LaTeX while simultaneously generating webpages or ePubs for electronic distribution. [1]: https://github.com/Wandmalfarbe/pandoc-latex-template
In How to write LaTeX without writing LaTeX
tlamponi·Apr 7, 2019
> OP won't try it out because it's unlikely the template will solve his issues His general issues in life? maybe not. But honestly, that's a bit of a big thing to ask from a pandoc template. So OP asked for it, implying that he's interested in such things, but generally has issues with long lines in such templates. So interest is there, it may even correlate with the fact that he has a setup with most of the tools needed installed. > playing around with new things is generally a waste of time What? I'm thankfully that a lot people do not think this way, else we'd be still in the stone age. > So if you (tlamponi) have some interest in promoting this template no interest whatsoever, not related to it in anyway. But I have an interest that people try easy things out, instead of speculating on negative or positive possibilities of said things
Read the rest
, which, in fact, is a waste of time. > but it is not as easy and straight-forward as you make it out to be. # package-manager install git pandoc # cd $(mktemp -d) # git clone https://github.com/Wandmalfarbe/pandoc-latex-template.git # cd pandoc-latex-template/examples # echo "Example for waste of time: 'Prediction: OP won't try it out because it's unlikely the template will solve his issues and playing around with new things is generally a waste of time. So if you (tlamponi) have some interest in promoting this template, then answering the question would be helpful! Everyone reading this submission is already aware that they could find things out by trying the template out, but it is not as easy and straight-forward as you make it out to be.'" >> basic-example/basic-example.md # sh build-examples.sh # okular basic-example/basic-example.pdf Ah yes, very very hard. Sorry for trying to convince someone to work out answers they're interested in their self, such a useless thing to do in life. Anyway, it seems that it does cope well with long lines, be it in a common text paragraph, but also in a code block, here it breaks those lines, intends the overflowing one - together with the fact that there are line numbers everything is clear and easy to read. Single thing, if I copy those broken up code lines, they do not get copied as a single line, this is a bit of a bummer to me, but may not be an issue for others..
In Eisvogel: A clean pandoc LaTeX template with a focus on computer science

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.