To be honest I'm not sure I want this feature. I rarely use the `pass $name` shortcut so I don't want to be prevented from using names that don't work with it.
Also it would be impossible to blacklist future command names although those are fairly infrequent. On Sep 13, 2016 08:27, "Steven Clarkson" <[email protected]> wrote: Hi, This is the first time I've done something like this, so sorry if it's not helpful or wrong, but I think it would be helpful if there was an error (or warning) when you tried to save a password with the same name as a command. For instance I inserted a password with the name git, then I couldn't access it without typing the full "pass show git", "pass git" tried to use the git features of pass. I'm assuming this would be the case if you named a password "help" or "init" or "list" as well. I think something simple like this would work? Or possible to define an array of command names that can't be used? If [[ $path -eq "help" || $path -eq "git" || etc. ]]; then echo "Cannot use Git or Help as password names" exit Is the proper process to branch the project then add my changes? Thanks, Steven _______________________________________________ Password-Store mailing list [email protected] http://lists.zx2c4.com/mailman/listinfo/password-store
_______________________________________________ Password-Store mailing list [email protected] http://lists.zx2c4.com/mailman/listinfo/password-store
