Summary

gopass init doesn't allow alternate root path

Steps To Reproduce

[~] 
>_ gopass init --path $HOME/foobar
[init] Initializing a new password store ...
Please select a private key for encrypting secrets:
[0] gpg - 0xD385289FA809234F - Matthieu Fronton <m@tthieu.fr>
Please enter the number of a key (0-0, [q]uit) [0]: 
[init] Initializing git repository (gitcli) ...

It would be great to have documentation on how to associate multiple keys + email id pairs in keybase and github for people using different account for open source and closed source work.

We still have docs describing an antigen plugin that has long been deprecated

The Getting Started page says:

Eventually you will want to push the local repo to a remote.

yadm remote add origin <url>
yadm push -u origin master

It wasn't clear to me whether to expect the yadm wrapper to be smart enough to exclude the internal repo path from <url> or not. It turns out it is not. Perhaps it would be clearer to use

Describe the bug/feature
I would like kapitan to output unindented sequences.
At the moment it generates

mylist:
  - item1
  - item2

and I want

mylist:
- item1
- item2

The current behaviour seems deliberate (https://github.com/deepmind/kapitan/blob/25f4ebaca159a748e44683a45875e74be73c1570/kapitan/utils.py#L163-L170 ) but I would like to be able to deactivate

Migration section in docs mentions

free password data from the clutches of other (bloated) password managers

what without providing more detailed comparison for a potential user sounds like "our password manager is missing many features".

If all important features are actually implemented, then it would be useful to show comparison matrix demonstrating this.

Ideally these should be pulled from some central location.

$ supybot --version
Limnoria 2019.10.05 running on Python 3.7.3 (default, Apr  3 2019, 05:39:12) 
[GCC 8.3.0]
$ supybot-adduser --version
supybot 2019.10.05
$ supybot-plugin-create --version
Supybot 2019.10.05
$ supybot-plugin-doc --version
Supybot 2019.10.05
$ supybot-reset-password --version
supybot 2019.10.05
$ supybo

Hi. general.tagbar_move isn't mentionned in https://github.com/astroidmail/astroid/wiki/Configuration-Reference and I couldn't understand what it did from reading astroid's source code. Could you update the wiki ? (or just answer here and I'll update it myself :))

the utility scripts overwrites existing files and configuration as it executes each instruction.
In case the script fails for some reason, all the modified files are left as it is, which sometimes corrupts the existing configuration.

It will be useful if the script backup relevant files and restore them in case of error.

A feature request: The very helpful example JSON format in the repo should be mentioned and linked to in the README. The IETF draft link may be useful for a small group of people wanting to dig deeper into the larger standardization effort around PGP key distribution, but for anyone wanting to get started making a keylist, it would be immediately helpful to mention what format it should be in.

When the git clone command referenced in this project's README file is used, the resulting project directory created in the local filesystem does not match the name used in the cd command that follows.

A PR (#6) has been submitted to correct this.

It would be nice if the documentation would how sheesy differentiates itself from a git-crypt.

So far as I can see currently:

• No integration with git
• No support for simple AES key encryption

Maybe it doesn't make sense to compare sheesy to a tool like git-crypt in the first place, since the scopes are somewhat different, if so I apologize! I think that sheezy could be super

Show the outputs of gopass config in a section of the settings screen