[pass] Printing full paths with show

[Von Welch]

> Then again, the beauty of KISS is that you don't need to use `pass show`
in scripts. You could just as
> well use `gpg -d`, for consuming cleartext passwords, or `ls`, for
showing subdirectory contents, directly.

Don't forget you need to recreate pass's logic around the finding the
password store and picking the right GPG key. Yes, it's great one can work
around pass to get at the password store, but it's non-trivial. You
basically start re-writing pass if you want to script any sort of direct
access to the store.

It would be nice if pass separated the logic from accessing the password
store from its UI a bit more cleanly.

Von


On Sun, Aug 2, 2015 at 2:05 PM Emil Lundberg <lundberg.emil at gmail.com>
wrote:

> > I will say 'pass [show]' acting differently when given a file or
> directory makes it hard to write scripts using it
>
> Then again, the beauty of KISS is that you don't need to use `pass show`
> in scripts. You could just as well use `gpg -d`, for consuming cleartext
> passwords, or `ls`, for showing subdirectory contents, directly.
>
> An exception to this, I guess, would be `pass show --clip`, which has some
> additional security features (such as resetting the clipboard after a
> timeout) you might want to reuse.
>
> On Sun, 2 Aug 2015 at 19:16 Von Welch <von at vwelch.com> wrote:
>
>> >I don’t understand why the „show“ subcommand even shows a tree.
>>
>> Since you mention it, I will say 'pass [show]' acting differently when
>> given a file or directory makes it hard to write scripts using it since
>> unless you look inside the password store to see if the argument is a
>> directory or file, pass is unpredictable in it's behavior and output.
>> Personally I'd rather see 'pass [show]' throw an error if given a directory
>> as an argument.
>>
>> Von
>>
>>
>> On Sun, Aug 2, 2015 at 8:47 AM Jakub Sokołowski <panswiata at gmail.com>
>> wrote:
>>
>>> Well, I've put it the cmd_show() because there was no cmd_ls() and
>>> creating it seemed like more of a challenge and big change to the script
>>> than I can manage correctly.
>>>
>>> I guess now that I think about it I can just use find, but the thing is
>>> I assume most people using pass don't really look into the inner
>>> workings of pass and would just like to have that kind of functionality
>>> available through the command. It seems more user friendly to me. Unless
>>> that's not what pass is aiming for.
>>>
>>> And thanks for the comment about git-send-email. I've never used it and
>>> I'm pretty new to this mailing list thingie. It seems pretty weird if
>>> you ask me, kinda archaic. But if it works it works.
>>>
>>> If this change does not fit pass that's fine. Thanks for the reply and
>>> the explanation.
>>>
>>> Cheers,
>>>
>>> On 02/08/15 14:29, Steffen Vogel wrote:
>>> > Hi,
>>> > thats a functionality I was also looking for already…
>>> >
>>> > But why did you extended the „show“ subcommand?
>>> > I think the „ls“ subcommand is the right place for this.
>>> >
>>> > I don’t understand why the „show“ subcommand even shows a tree.
>>> >
>>> > Alternatively, you could bypass pass completely by using:
>>> >
>>> >     find ~/.password-store -name -type f -name „*.gpg“
>>> >
>>> > I think, thats an easier way to accomplish this.
>>> >
>>> > Cheers,
>>> >
>>> > Steffen
>>> >
>>> > —
>>> >
>>> > Steffen Vogel
>>> > Robensstraße 69
>>> > 52070 Aachen
>>> >
>>> > Mail: post at steffenvogel.de
>>> > Mobil: +49 1575 7180927
>>> > Web: http://www.steffenvogel.de
>>> > Jabber: steffen.vogel at jabber.rwth-aachen.de
>>> >
>>> >> Am 02.08.2015 um 13:42 schrieb Jakub Sokołowski <panswiata at gmail.com
>>> >:
>>> >>
>>> >> Hi,
>>> >>
>>> >> I really love pass and I wanted to extend it by passing it's output
>>> to fzf(https://github.com/junegunn/fzf) to easilly search through
>>> available entries. Unfortunately the current output format makes it
>>> impossible to easilly use it for fzf.
>>> >>
>>> >> So I propose the following patch to add an -f,--full(same as for
>>> tree) options to print out the list with full paths.
>>> >>
>>> >> This way one can easily use pass and fzf in following way:
>>> >>
>>> >> pass -f | fzf | xargs -I{} pass -- {}
>>> >>
>>> >> Which in a trivial way gives a fuzzy search ability to pass.
>>> >>
>>> >> I'm not sure if this approach is the best but I've used it
>>> successfully for a while now. I think it could be useful to more people.
>>> >>
>>> >> Cheers!
>>> >>
>>> <show_full_option.patch>_______________________________________________
>>> >> Password-Store mailing list
>>> >> Password-Store at lists.zx2c4.com
>>> >> http://lists.zx2c4.com/mailman/listinfo/password-store
>>> >
>>> >
>>> >
>>> > _______________________________________________
>>> > Password-Store mailing list
>>> > Password-Store at lists.zx2c4.com
>>> > http://lists.zx2c4.com/mailman/listinfo/password-store
>>> >
>>> _______________________________________________
>>> Password-Store mailing list
>>> Password-Store at lists.zx2c4.com
>>> http://lists.zx2c4.com/mailman/listinfo/password-store
>>>
>> _______________________________________________
>> Password-Store mailing list
>> Password-Store at lists.zx2c4.com
>> http://lists.zx2c4.com/mailman/listinfo/password-store
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zx2c4.com/pipermail/password-store/attachments/20150802/6c9247b1/attachment.html>