On Wed, Feb 07, 2018 at 11:36:29PM +, Tobias Girstmair wrote:
> I'm confused as to why this patch comes to be. Using the env.var works quite
> well to set which selection pass shall use. (e.g.
> `PASSWORD_STORE_X_SELECTION=primary pass -c git` puts my git password into
> the primary (== midd
You are right, I forgot about your comment when I started to actually
add this feature.
How about `-p` and `--prim`? It could be very symmetric to `-c` and
`--clip`. Now that I'm thinking about it, perhaps this way we don't even
need `$PASSWORD_STORE_DEFAULT_X_SELECTION` or
`$PASSWORD_STORE_X_SELE
I think using -C for this is a bad idea since the conventional meaning
of -C is to allow changing the working directory, and I think this
would be a useful feature for Password Store (because it seems rather
odd to me that the path to ~/.password-store is completely hardcoded).
I like the actual fe
I'm confused as to why this patch comes to be. Using the env.var works quite
well to set which selection pass shall use. (e.g.
`PASSWORD_STORE_X_SELECTION=primary pass -c git` puts my git password into the
primary (== middle click) selection as expected)
about the patch itself:
- renaming the e