Hi Shawn, all, Thanks, I read on the documentation that that is one option. However, all my ~1000 passwords are arranged in the form of encrypted files with both passwords and usernames, so I'd prefer to keep usernames inside the files for now. I guess some users might also prefer it this way for privacy reasons, so usernames are not readable to someone without the GPG key.
I've not got a great deal of experience with bash scripting, but it seems like this should be reasonably simple to add. Is this something the developers would accept a patch for? Cheers, Sean On 18/06/2020 16:44, Shawn Turpin wrote: > What I have typically done is do a password generate/insert like this: > > pass generate /my/password/file/loginname > > Or another for more of a real example > > pass generate /websites/amazon.com/my-really-cool-username > <http://amazon.com/my-really-cool-username> > > That way your password is associated with your username. > > Cheers, Shawn > > On Wed, Jun 17, 2020 at 11:47 PM <[email protected] > <mailto:[email protected]>> wrote: > > Hi pass users, > > Is there an equivalent to the -m flag of `pass insert` for `pass > generate`? Essentially 100% of the time I want to store my username next > to the password in the file, and have to do `pass generate > my/password/file` then `pass edit my/password/file`, generating two git > commits and forcing me to type my password the second time. Maybe I'm > doing it wrong, but if not, it would be nice if there could be an option > for `pass generate` that also prompts for extra information to add to > the file, where I could add my username etc., to prevent me having to > make a subsequent edit. > > Cheers, > > > Sean >
