Stuart Henderson <[email protected]> wrote: > On 2018/08/02 12:26, Frederic Cambus wrote: > > On Wed, Jul 25, 2018 at 08:30:59PM +0200, Frederic Cambus wrote: > > > > > Here is a new port: textproc/miller. > > > > > > From DESCR: > > > > > > Miller operates on key-value-pair data while the familiar Unix tools > > > operate > > > on integer-indexed fields: if the natural data structure for the latter > > > is the > > > array, then Miller's natural data structure is the insertion-ordered hash > > > map. > > > This encompasses a variety of data formats, including but not limited to > > > the > > > familiar CSV, TSV, and JSON. Miller can handle positionally-indexed data > > > as > > > a special case. > > > > > > Comments? OK? > > > > Ping. Anyone willing to look at this? > > > > DESCR doesn't do a great job of selling it - it seems something akin to jq > but handles more input formats, but that DESCR doesn't really show it. How > about a bit more borrowed from http://johnkerl.org/miller/doc/? > > ==== > Miller (mlr) is like awk, sed, cut, join, and sort for name-indexed data > such as CSV, TSV, and tabular JSON. You get to work with your data using > named fields, without needing to count positional column indices. It is > pipe-friendly and interoperates with the Unix toolkit. > > It operates on key-value-pair data while the familiar Unix tools operate > on integer-indexed fields. This encompasses a variety of data formats, > including but not limited to the familiar CSV, TSV, and JSON. (Miller > can handle positionally-indexed data as a special case.) > ==== > > OK either way.
I agree that this DESCR is more explanative about the software than the current one.
