hi. i put the following very small patch together for
pass.bash-completion. it allows one to specify an environmental
variable PASSWORD_COMPLETE_ENTRIES, which is shell code that is "eval"d.
the default is (we hope) the current behavior. but, i, e.g., have in my
.bashrc, the following:
On 18-05-12 15:22, Philippe Biondi wrote:
> William Morris <m...@williammorris.com> writes:
>
> > I like this but I wonder if it might make more sense to implement this
> > as an extension.
>
> I see this more as an improvement of the UI than an alternate mod
William Morris <m...@williammorris.com> writes:
> I like this but I wonder if it might make more sense to implement this
> as an extension.
I see this more as an improvement of the UI than an alternate mode. In
my case, "pass choose" completely replaced "pass find&
ion. But once the path
> I'm looking for has been found, I find it painful to enter it again with
> a new invocation of "pass". Even more painful that I already entered
> enough to find it.
>
> So I wrote this little quick patch to add a "choose" command:
>
>
ready entered
enough to find it.
So I wrote this little quick patch to add a "choose" command:
pass choose [pass-names...]
List passwords that match pass-names and ask to choose one
It works a lot like "pass find", except that:
- when only one file has been found
