Devin Lehmacher writes:
> If I’m not mistaken magit won’t stop working with the changed
> location since it will just spawn an new instance of the
> daemon. The only downside would be it wouldn’t get credentials
> that were cached in the default socket.
I am not quite sure
If I’m not mistaken magit won’t stop working with the changed location since it
will just spawn an new instance of the daemon. The only downside would be it
wouldn’t get credentials that were cached in the default socket.
I am going to move forward with git-credential-cache just using the new
On Fri, Mar 10, 2017 at 7:26 PM, Jonathan Nieder wrote:
> I find that magit does rely on the socket path.
>
> Start credential daemon on magit-credential-hook
>
> If we let git start the daemon, Emacs will send a SIGHUP when git
> finishes and closes the pty,
(+cc: npostavs)
Hi Devin,
Devin Lehmacher wrote:
> I started working on this microproject and am not quite sure what is
> necessary for backwards compatibility. Since the socket is recreated
> whenever the credential daemon exits backwards compatibility
> shouldn’t really be a concern with
I started working on this microproject and am not quite sure what is necessary
for backwards compatibility. Since the socket is recreated whenever the
credential daemon exits backwards compatibility shouldn’t really be a concern
with regard to where the socket is located in the filesystem.
5 matches
Mail list logo