The first way I did it was just read the file, parse the json, check for nulls, and print. Then I piped this to a file. That is too boring though. The next way

The first way I did it was just read the file, parse the json, check for nulls, and print. Then I piped this to a file. That is too boring though. The next way I did it was with Vim replaces. There might be sexier ways of doing this? 1) A big replace to get rid of all the junk. %s/\%Vemail.*creditcard/creditcard/g 2) A big replace to fix nulls in the credit card %s/\%V.*creditcard.*null.*//g Then I could either change my code to not check for nulls or keep cleaning up this data until I have a CSV. This Vim flow is the exact thing I do every week or two at work when building the Chrome HSTS preload list into our product. Anyone know the sexier ways to make this really really fun? I should note to those not super familiar with vim that may try this, my vim commands are over a visual block (the json string), since this was in the same file as my code.