The whole motivation for pass was not to have anything that needs an API or an interface to work with. The interface is the filesystem. Each password is in a file. Files can be dealt with through the gpg tools. Scripts are to just use the ordinary filesystem APIs to do what they need to do. pass itself is one such script that uses those filesystem APIs for the purpose of having a nice terminal frontend.
Maybe pass has become too complicated since this original mission, and now some sort of abstracted generic monstrosity is needed. If this is the case, what a shame. But with that said, I wouldn't oppose making changes so that pass's output is more easily scriptable. For example, testing [[ -t 0 ]] and outputting different things might be worthwhile. What do your scripts need to do? Maybe folks on the list can help you find the most direct solution for your scripting needs? _______________________________________________ Password-Store mailing list [email protected] http://lists.zx2c4.com/mailman/listinfo/password-store
