Correct, but that env var is not obvious until looking at the code and the ‘-C dir’ option is not uncommon for other tools (like git, tar).
More context: at work we're using pass for managing many project secrets which are scoped per project and not in the user profile folder. Switching between folders is a lot easier (and looks less hacky) with `pass -C . …` compared to `env PASSWORD_STORE_DIR=. pass …`. Having this switching the store_dir as a first-class supported option, knowing to the "prior-art” of other tools and the small size of the diff, it seems like a good idea for inclusion into pass. Lio. > On 31 Jan 2019, at 05:32, Reto Brunner <[email protected]> wrote: > > Whats wrong with just setting PASSWORD_STORE_DIR? > Both can be done from the command line or a script, I don't see the benefit > of changing it to a parameter instead. > > Can you enlighten me? > _______________________________________________ > Password-Store mailing list > [email protected] > https://lists.zx2c4.com/mailman/listinfo/password-store _______________________________________________ Password-Store mailing list [email protected] https://lists.zx2c4.com/mailman/listinfo/password-store
