On Thu, Oct 29, 2015 at 8:50 PM, Jeff King <peff@xxxxxxxx> wrote: > workaround (the real inelegance is that you are assuming that "foo" > needs run in the first place). Well, we currently check the output from "git config credential.helpers" to determine what's needed, so the inelegance here is that we reimplement git's checking of this option. > I'm still not sure how the pre-helper would work. What git command kicks > off the pre-helper command? Wouldn't it also be subject to the SIGHUP > problem? Ah, maybe the missing piece I forgot to mention is that we could make our pre/1st-helper be an emacsclient command, which would tell Emacs to startup the daemon. So the daemon would be a subprocess of Emacs, not "git push", thereby avoiding the SIGHUP. In our current workaround we startup the daemon (if it's not running) before git commands that we think are going to run credential helpers (i.e. "push", "pull", "fetch"), hence my thought that it would be nicer if we only did that before git is *actually* going to run the helpers. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html