top | item 46327608 (no title) Thom2000 | 2 months ago I wonder if they think of a deeper integration of this into the age binary. Currently the invocation looks extremely ugly: age -r $(go run filippo.io/torchwood/cmd/age-keylookup@main joe@example.com) discuss order hn newest akerl_|2 months ago I assume once it's stabilized you'd swap the `go run` for just installing and using a binary, similar to what you're already doing with age. FiloSottile|2 months ago Honestly not sure why I didn't do that once the tool had stabilized.Switched to go install filippo.io/torchwood/cmd/age-keylookup@main age -r $(age-keylookup alice@example.com) age is designed to be composable and very stable, and this shell combination works well enough, so it's unlikely we'll build it straight into age(1). load replies (1)
akerl_|2 months ago I assume once it's stabilized you'd swap the `go run` for just installing and using a binary, similar to what you're already doing with age. FiloSottile|2 months ago Honestly not sure why I didn't do that once the tool had stabilized.Switched to go install filippo.io/torchwood/cmd/age-keylookup@main age -r $(age-keylookup alice@example.com) age is designed to be composable and very stable, and this shell combination works well enough, so it's unlikely we'll build it straight into age(1). load replies (1)
FiloSottile|2 months ago Honestly not sure why I didn't do that once the tool had stabilized.Switched to go install filippo.io/torchwood/cmd/age-keylookup@main age -r $(age-keylookup alice@example.com) age is designed to be composable and very stable, and this shell combination works well enough, so it's unlikely we'll build it straight into age(1). load replies (1)
akerl_|2 months ago
FiloSottile|2 months ago
Switched to
age is designed to be composable and very stable, and this shell combination works well enough, so it's unlikely we'll build it straight into age(1).