texlive-batch-installation VS awk

The Problem is that TeXLive still defaults to doing a full install.

A full install means installing ~4000 packages, including their source files (tens of thousands of tex files) and built documentation (thousands of PDF files) and hundreds of free fonts (otfs, ttfs, texs own format).

This is huge (>7GB, not just the 5 GB claimed here).

However, you don't need 99 % of this for any given document.

Not installing the source files and documentation PDFs will alone reduce the size by roughly half.

Only installing the packages you really need from a minimal installation gives you a few hundred megabytes at most for even complex documents.

It's a bit annoying to get the list of packages needed though, since there is not really any working dependency management.

I wrote a python wrapper around the tex live installer [1] to make this easy for CI jobs, see e.g. [2].

On a side note: I'd recommend luatex over xetex.

- [1] https://github.com/maxnoe/texlive-batch-installation/

- [2] https://github.com/pep-dortmund/toolbox-workshop/blob/8b00f0...

Awk now supports a `--csv` flag for processing csv's. https://github.com/onetrueawk/awk/blob/master/README.md

Right, "the one true awk" corresponds to a book written in 1988, very explicity. https://github.com/onetrueawk/awk

You were the one that that said POSIX awk to begin with, I was using your terms.

As far as shitting on the GMU tools, I don't think I've seen someone do that for over 20 years.

This is not a productive conversation. You can live life however you want

I also wrote a small program to benchmark and check the solutions across different Awk implementations (see the image). I use the macos system awk (which is pretty close to https://github.com/onetrueawk/awk if I'm not mistaken) as a reference (the first column), so all solutions had to work with that.

A simpler Yacc grammar is awk/awkgram.y.

Neat, this is now the third year I'm using awk and still learning new tricks. (I'm using awk as the reference, so I don't use gnu extensions.)

I did this in nawk, which doesn't support extended regular expressions. If instead you're using gawk, which does, check out \b for word boundaries in extended regular expressions. The [^a-z][a-z] approach you showed consumes the prior character.

BWK’s commit and test files (mentioned in the video)

https://github.com/onetrueawk/awk/commit/d3a19e6f2533d479841...

git clone -b unicode-support https://github.com/onetrueawk/awk.git

This is dumb as fuck. Brian Kernighan of K&R (The C Programming Language) is 80 and he’s still more intelligent than any of you retards. Mf just submitted a patch to awk a couple months ago https://github.com/onetrueawk/awk

The Unicode branch: https://github.com/onetrueawk/awk/tree/unicode-support