Suppose one would like to process compiler output to include span; vim uses awk (mve.awk) to do this.
I am in the process of adding a deduplication builtin to my Jacinda language. It's something I've wanted often enough and evidently part of the reason people use awk (it is the way to deduplicate on the command line without changing order).
One can use Jacinda to generate tags files for vim. This amounts to string processing with regular expressions, which we can do in a functional style, skirting Universal Ctags.
Suppose we wish to inspect our PATH. Then we can make it more readable using
awk:
GHC includes span information in compiler errors, but not in a format suitable for vim:
prev | next