If it's the case, "gvim -f" would help. On Fri, Dec 2, 2016 at 4:03 AM, Kevin Cox <[email protected]> wrote:
> On 02/12/16 11:13, ads wrote: > >> Thanks for the suggestion. >> >> I looked at strace, but couldn't see any obvious cause (no EPERM for >> example). I set up a new user where it all worked properly, so I started >> to try and find a difference, and realised that my normal userid uses gvim >> (echo $EDITOR --> gvim) while my new test user uses vim. So to make the >> straces comparable I switched to using vim for this task, but using vim I >> find works fine anyway. I don't really need to find out why gvim doesn't >> work since I have a good work-around, i.e. preface the pass edit command >> with EDITOR=vim. >> > I think that gvim detaches by default, so when it "exits" pass saves the > (unchanged) file. Then you edit the file but pass is long gone. > > There might be a flag you can set to make it "block" or stay in the > foreground. That or use a different editor. > > _______________________________________________ > Password-Store mailing list > [email protected] > https://lists.zx2c4.com/mailman/listinfo/password-store > -- Best wishes Kun Zhang
_______________________________________________ Password-Store mailing list [email protected] https://lists.zx2c4.com/mailman/listinfo/password-store
