md2pdf VS bottom

Here is a small command line tool: https://github.com/jmaupetit/md2pdf

Document read from codimd-api https://github.com/hackmdio/hackmd-cli/blob/master/README.md - Matching config.yaml + styles read from git - Fetching data from CRM https://docs.espocrm.com/development/api/#client-implementations - Parsing markdown as jinja template - Generate pdf from markdown https://github.com/jmaupetit/md2pdf - Add signature fields https://github.com/MatthiasValvekens/pyHanko - store pdf file (maybe seafile?) (or nextcloud)

Writing Documents Markdown (and md2pdf or cmark + html2ps + ps2pdf) / plain text / groff

bottom

I'd suggest Bottom as a TUI alternative to the in-built task managers - https://github.com/ClementTsang/bottom

It works on Windows also.

If anyone is looking for a "top" like, written in Rust, might have a look at https://github.com/ClementTsang/bottom

Looks like bottom with another theme

bottom - A cross-platform graphical process/system monitor with a customizable interface and a multitude of features.

As a macOS user, it boils my brain whenever I've to type in something like ~/Library/Application Support/org.rust-lang.Cargo/config.toml. macOS users have been begging CLI tools to support XDG variables on macOS too. Setting defaults is a strong indication to the community what should be the "preferred" locations. The defaults defined in your article will invariably lead to some authors saying that if that path is good enough for cargo, then it is good enough for their tool. Even the latest draft RFC acknowledges that macOS should use XDG variables too. I've written more about this here.