AnomalRoil

Running `gopass fsck` correctly fixes the issue of lack of proper git config of the password store after having used `gopass clone ...`

Don't do the `gopass init` at all. Delete everything again and try directly with: ``` gopass clone [email protected] gopass fsck ``` That fsck step should check that everything is working...

If you go to the password store folder, typically `~/.local/share/gopass/root` and you use git there directly, what does the following tell you: ``` git status git log git remote -v...

What does `git branch -a` tell you? (Also, you might want to hop on our Slack channel to try and debug that, because currently we cannot reproduce it, so it...

Having individual settings for different mounts was deprecated in 1.10 actually. I don't remember the exact rational, but the goal is to simplify the codebase and to have as little...

@dominikschulz I can see how having mount-specific config options can be useful. Should we have a user-story with this ^ usecase and include it back? I don't know how much...

The way we did config and per-store config previously was cumbersome. But IMO we could probably come up with a better scheme. For example, for the "per-repo" config: what if...

I guess we could add a environment variable to disable it. Currently we are just using regex on the .vimrc file, where are you config stored?? https://github.com/gopasspw/gopass/blob/d00c29a0e8e521eb32e4564998690430dcc7dbbc/internal/editor/editor.go#L36

Otherwise we could use a dotfile within the password store. Like: do not check warning if there is a `.nogopasswarning` file in the password store...

This should be patched by #2239 @daiaji Can you try v1.14.3 and report if it now works as expected on your side?