Jeremy Hooke

I just noticed you commited a large rewrite to master an hour ago. I haven't tested this with the new version yet.

This is great. The inconsistency between pseudo-elements and other simple-selectors (like attribute selectors) has always bugged me. I like the backticks. They aren't as visually noisy as the other characters.

I've removed the paragraph. In hindsight it wasn't worth mentioning.

I like `apply`. I wouldn’t rush to remove the old ones as there’s lots of bash scripts, beginners-guides, power point presentations and tutorials that have them. I do like the...

Another option is not to remove the old ones entirely, but just make them aliases for the new command. In effect, retiring the more niche options/flags that they take. Beginner...

Yes, I think so. We have only implemented `archive` so far because we want to keep a record of every historical dataset — primarily for provenance. Once archived, a dataset...

I'm seeing this too. Is there a reasonable workaround to tell it to treat the shell as normal bash?

Vacuum commands too, for reference: ``` vacuum analyze agdc.dataset, agdc.dataset_type, agdc.dataset_source, agdc.metadata_type, agdc.dataset_location, cubedash.dataset_spatial, cubedash.product, cubedash.region, cubedash.time_overview; ```

Thanks Pin. To copy your Slack discovery here: it's because the other two have no datasets, and so they're not included in the materialised view query results. It sounds useful...

The header means "73 products have summaries, and no products are missing summaries.". Perhaps we could clarify it.