[–] 2 points 1 month ago (2 children)

I personally never had a case where Typst couldn't do what I wanted and usually found something better in Typst instead. The only exception is to do curly snake-like rectangle borders, but it's probably doable in Cetz.

As for hyperref, you are propably right, I would personally use a boolean flag for that and do two versions. Though the whole point of a pdf is to have the same look between it and the print, other features might fail depending on the viewer.

I think the extra spaces in math make it more readable, and it's kinda the price to pay to not have to add backslashes everywhere. One instance when I found it weird was that frak("abc") had a different font than frak(a b c). So i just make a #let abc = $frak( a b c)$ rule.

  • source
  • parent
  • context
  • [–] 2 points 2 months ago

    I read a reddit thread about this.

    Basically they are significantly safer because the review process is tedious and the PRs take ages to get reviewed. More over the read-only nature of the nix store make most of those techniques useless. You cannnot just take over packages the AUR way.

    Moreover, if you use third party nix flakes, you are still safer because they are tied to a specific github repo, so if it gets forked by malicious actor you won't get that update.

    However you are still prone to upstream malware. That is nixpkgs probably won't add malware but it could be there before packaging.

  • source
  • parent
  • context
  • view more: next ›