Troff seems to be one of the better options. Luke Smith has some tutorials on
using troff and groff
here: https://www.youtube.com/playlist?list=PL-p5XmQHB_JRe2YeaMjPTKXSc5FqJZ_km
For live previewing I suggest zathura instead of mupdf, since zathura
automatically refreshes
when it detects changes
HTML renderers are vast and somewhat easy to code, depending how far
you want to go.
After seeing that css4.pub website, it has opened my eyes: why are we
doing Markdown at all?
If we stick to using tags like header, article, main, div, p,
ul/ol/li, and maybe a few others, what more do we really
On Mon 29 Apr 2019 at 02:53:10 PDT Przemek Dragańczuk wrote:
Troff seems to be one of the better options. Luke Smith has some tutorials on
using troff and groff
here: https://www.youtube.com/playlist?list=PL-p5XmQHB_JRe2YeaMjPTKXSc5FqJZ_km
For live previewing I suggest zathura instead of mupd
niedz., 28 kwi 2019 o 21:46 Thomas Meulendijks
napisał(a):
>
> Hi all,
>
> I am currently using pandoc to convert my markdown files into pdf.
> I do this because of a few things,
>
> - I want to be able to manage my documents in git.
> - I want to edit my documents in my text editor of choice
> -
If this has (de)evolved into a general sucks less document writing thread, I
too would recommend {g,t}roff. Luke Smith’s YouTube series is a good intro for
the impatient. OpenBSD’s manpage for roff is an excellent read over coffee:
https://man.openbsd.org/roff.7
On 2019-04-29 09:06, Charlie Kester wrote:
> And doesn't zathura use poppler, which is bloated and slow compared to
> mupdf?
Zathura can use mupdf as a PDF/EPUB/XPS backend.
--
Stephen Gregoratto
PGP: 3FC6 3D0E 2801 C348 1C44 2D34 A80C 0F8E 8BAB EC8B
