Well, I am not a fan of asking user, too. Other thing that came in to my
mind when designing was:
- if there is exactly one password matching, descrypt
- otherwise print all matches and exit.
That would not need any new 'sub-command'. It would be alteration of find
command.
What I did not want to do, is decrypting everything.
Also the aim is - to provide password faster, if user knows what to search
for.
On utorok 14. aprÃla 2020 19:15:15 CEST, Tobias Girstmair wrote:
On Tue, Apr 14, 2020 at 06:20:07PM +0200, Michal Klempa wrote:
I was wondering if command searching through passwords in
store and immediately asking whether to print desired password
would be useful. Tried a little and I came with small code as a
draft for discussion and proposal.
In my opinion, this doesn't feel like a proper pass/UNIX
behaviour, with it asking for user input repeatedly. There has
been the proposal in the past to make pass find show complete
paths [1], which would allow you to put it into primary
selection and pasting it very easily, but I remember this not
going anywhere. That said, I'm following this mail up with such
a patch.
[1]: either based on find(1), or using something like `tree
-Ffi | grep -v '/$'`
