On Fri, 2 Aug 2019, Sven Schreiber wrote:
Am 01.08.2019 um 21:42 schrieb Allin Cottrell:
> On Thu, 1 Aug 2019, Artur Tarassow wrote: > >> I also think that
> implementing it natively either through a >>
function or command extension is the right way. adding an option >> to
the pkg command looks quite natural to me. > > Here's what's in current
git (snapshots and documentation to > follow): there's a new "query"
action for the pkg command. By default > it prints information and
stores nothing, but with the --quiet option > it prints nothing and
stores a $result bundle.
Thanks Allin. But couldn't it always store (or overwrite) the $result
bundle, even without --quiet? It feels a bit strange to have to tell it
to shut up (quiet) just to get the output somewhere else.
My thought was/is that it's not worth wasting CPU cycles setting up
a stored bundle unless that's actually what's wanted; and it's
unlikely that anyone wants both the printout and the bundle.
I suppose the --quiet option could be renamed as --store or --bundle
or similar, with the side effect of quietness, rather than the
converse.
Allin