htmlq

honourable mention for HTML: https://github.com/mgdm/htmlq

The issue with CSS selectors is they can only express element selection. There's no concept of picking the text of the element or the value of an attribute. There's been proposals over the years to support pseudo elements for that, so you could make something up like ::attr(name) and ::text, but nothing in the standards. htmlq does this by having various command line options like --attribute and --text. https://github.com/mgdm/htmlq#examples

Hey, author here, happy to answer questions! A few other recent posts/tools that you may be interested in: - sqlite-lines discussion from a few days ago: https://news.ycombinator.com/item?id=32288165 - htmlq, Rust CLI for (like jq but for html): https://github.com/mgdm/htmlq - The Go library that sqlite-html uses for making runtime-loadable SQLite extensions https://github.com/riyaz-ali/sqlite - sqlean, a ton of other helpful SQLite extensions (in C): https://github.com/nalgeon/sqlean

On that note, this is the shell alias I use to remember status codes (using htmlq https://github.com/mgdm/htmlq): alias status_codes="curl --silent https://developer.mozilla.org/en-US/docs/Web/HTTP/Status | htmlq --text 'dt a code'" Prints something like this: 100 Continue 101 Switching Protocols 102 Processing 103 Early Hints 200 OK 201 Created 202 Accepted 203 Non-Authoritative Information 204 No Content 205 Reset Content 206 Partial Content ... To get specific groups, I do something like this: status_codes | grep ^2 Replacing 2 with whatever group you want, like 4 for 4xx codes for example

Ah, htmlq [1] is a missing one that's not on the list! Straight from the repo: "Like jq, but for HTML." I find it useful for quickly hacking scripts together and exploring data. Very useful for the iterative process of finding good CSS selectors with the data that I can get without javascript running. --- [1] https://github.com/mgdm/htmlq

Stepping just a little beyond regular ‘loop and filter’ is already difficult without consulting the manual each time — being exacerbated by the impossibility of finding those things in the manual without skimming through most of it. Making an ‘if’ for variations in the input structure is easily a twenty-minute job. Outside of the basic features, Jq's syntax is increasingly arcane and unintuitive—maybe those working with it daily do remember the ‘advanced’ stuff, but I don't. I actually collected a sizable list of alternatives to Jq: https://github.com/TomConlin/json2xpath https://github.com/antonmedv/fx https://github.com/simeji/jid https://github.com/jmespath/jp https://jsonnet.org https://github.com/borkdude/jet https://github.com/jzelinskie/faq https://github.com/dflemstr/rq https://github.com/mgdm/htmlq And there's someone else's list