Tootfinder

@… Je viens just de vérifier, pour mon rapport d’activité, j'ai utilisé #Pandoc avec #TexLaTeX comme backend.

@… Je viens just de vérifier, pour mon rapport d’activité, j’utilisais encore #Pandoc avec #TexLaTeX comme backend. Mais peu importe, on pourrait facilement le remplace…

from my link log —
Twenty years of Pandoc.
https://pandoc.org/twenty-years-of-pandoc.html
saved 2026-08-03 https://dotat.at/:/IA2…

@… Ce serait #TexLaTeX ;-)
Mais moi, je préférerais #Pandoc avec #Typst

@… Ce serait #TexLaTeX ;-)
Mais moi, je préférerais #Pandoc avec #Typst

A cool history of, and some reflections on Pandoc, by its developer (and philosopher) John MacFarlane: #pandoc

I figured out a simple way to do callout boxes in pandoc's markdown, and having fiddled with it all morning, I am posting about it in case anyone is interested: https://codeberg.org/ddrake/simple_pandoc_callouts/

Yes, the command line can be powerful, but I was tired of spinning up a terminal window regularly only to convert a #Markdown file to a certain output format with #pandoc. So to scratch my own itch, I wrote a small python extension for

I didn’t reply to any messages yesterday; instead, I moved my remaining #Pandoc filters to Codeberg and updated the blogpost:
https://dynalabs.de/mxp/blog/2026-06-17
The makefiles in these pack…

Filters, Filters, Filters

@… I’m using #Pandoc with #Typst as backend (with this quick’n’dirty template, and with

@… I’m using #Pandoc with #Typst as backend (with this quick’n’dirty template, and with

So ist das schön. Mit CopyQ (https://hluk.github.io/CopyQ/) kann ich nun den Clipboard-Content via Pandoc einfach zu Mediawiki > Markdown und umgekehrt formatieren.
Außerdem wird sämtlicher "RichText" (i.d.R. HTML)-Content in nem Tab "auto-markdown" automatisch als Markdown zum dire…

@… I split my publications into several BibTeX files according to type and use the multibib filter (https://github.com/pandoc-ext/multibib) and the apa-c…

@… I split my publications into several BibTeX files according to type and use the multibib filter (https://github.com/pandoc-ext/multibib) and the apa-c…

I didn’t reply to any messages yesterday; instead, I moved my remaining #Pandoc filters to Codeberg and updated the blogpost:
https://dynalabs.de/mxp/blog/2026-06-17
The makefiles in these pack…

I didn’t reply to any messages yesterday; instead, I moved my remaining #Pandoc filters to Codeberg and updated the blogpost:
https://dynalabs.de/mxp/blog/2026-06-17
The makefiles in these pack…

@… For me, this is, of course, #Emacs. For formatting, I run #Pandoc via make.

@… For me, this is, of course, #Emacs. For formatting, I run #Pandoc via make.

Maybe the answer is somehow hooking up Pandoc for docstrings 🤪

@… I don't use Windows, but I guess that the issue is that you need to call pandoc from the command line.
You may want to look at applications that integrate pandoc in a more accessible fashion, e.g., @….

@… I don't use Windows, but I guess that the issue is that you need to call pandoc from the command line.
You may want to look at applications that integrate pandoc in a more accessible fashion, e.g., @….

@… @… I guess the issue is that there’s no standard syntax for cross references. If you restrict yourself to, say, pandoc Markdown with explicit IDs, it’s trivial to implement.

@… @… I guess the issue is that there’s no standard syntax for cross references. If you restrict yourself to, say, pandoc Markdown with explicit IDs, it’s trivial to implement.

I used to have one subdir/repo per course PLUS a pandoc directory (on the same level) with common settings for all courses.
What’s the best approach to share the whole? One repo for everything? Or one repo for the common stuff and separate repos for each course, and use #gitsubtree?
Or just separate repos? Because subtrees seem to be rather designed for the reverse scenario.

I used to have one subdir/repo per course PLUS a pandoc directory (on the same level) with common settings for all courses.
What’s the best approach to share the whole? One repo for everything? Or one repo for the common stuff and separate repos for each course, and use #gitsubtree?
Or just separate repos? Because subtrees seem to be rather designed for the reverse scenario.

@… I have effectively switched to Typst (https://dynalabs.de/mxp/blog/2026-02-10), but ACM requires LaTeX (which I generate via pandoc).

@… I have effectively switched to Typst (https://dynalabs.de/mxp/blog/2026-02-10), but ACM requires LaTeX (which I generate via pandoc).

@… @… Ça aussi, c’est la beauté de pandoc: chacun peut utiliser sa syntaxe préférée ;-)
Pour ce genre de documents en particulier, ce sont surtout les listes de publications selon des critères spécifiques et les tableaux de toutes…

@… @… Ça aussi, c’est la beauté de pandoc: chacun peut utiliser sa syntaxe préférée ;-)
Pour ce genre de documents en particulier, ce sont surtout les listes de publications selon des critères spécifiques et les tableaux de toutes…