Searching currently prints a tree(1) with the results, eg:
$ pass search wine
Search Terms: wine
└── www
├── issue-trackers
│ └── winehq-bugs
├── winehq-appdb
└── winehq-bugzilla
I feel that using find(1) insted would yield results which are more consistent
with the arguments that pass(1) can receive:
$ cd $HOME/.password-store
$ find * -iname "*wine*" | sed 's/\.gpg$//'
www/issue-trackers/winehq-bugs
www/winehq-appdb
www/winehq-bugzilla
The strings returned by using find(1) are exactly the format that pass(1)
expects, so we can be even more unixy:
pass show $(pass search openerp | tail -n 1)
# I alredy know this returns just one result
Personally, I'd also get rid the line that says "Search Terms: $TERMS"; I feel
that it's redundant and also pollutes the output a bit. Also, users could do
could just do:
pass show $(pass search openerp)
Any opinions on this?
Cheers!
--
Hugo Osvaldo Barrera
A: Because we read from top to bottom, left to right.
Q: Why should I start my reply below the quoted text?
pgp0QWIA50OxF.pgp
Description: PGP signature
_______________________________________________ Password-Store mailing list [email protected] http://lists.zx2c4.com/mailman/listinfo/password-store
