Change:
Describe the bug When using Sublime-Merge, pushing to remote results in an error message: To Reproduce Steps to reproduce the behavior: both sublime-merge and git. a repository. something, so that the local master is ahead of the remote. a push. Expected behavior A password prompt appears, and the push continues as normal. Additional context Some earlier discussion occurred in on the Sublime team's own github. We eventually found that the for sublime-merge seems to build, patch, and then discard a copy of . This may be the source of the issue. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Please run and paste the result. Output: Maintainer information:
Hi Thanks for letting me know, I've never tried entering a SSH passphrase directly through Sublime Merge before so I've never run into this issue, my ssh-agent just always handles it. I can say that the binary IS being included by the nix package and that the executable is finding and executing it properly (I confirmed this with strace), however for whatever reason the executable is just not creating the popup to ask for the passphrase and I don't understand why. I've followed up with the Sublime Merge team in , hopefully they will get back to me with some context about what the executable is looking for so that we can update the package to provide that.
So after discussing this with the helpful folks on the Sublime Merge repository, I was able to figure out what the problem is, it is happening because the functionality for actually depends on passing a special value as the to the executable. However the file that is trying to pass the to is actually a wrapper script that calls to run the actual binary after setting up the proper environment variables. There doesn't appear to be any way for the bash script to detect the argv[0] that was passed to bash as $0 is overwritten with the path to the bash script. I'm not sure how we will resolve this issue but at least we know what is causing it now. Maybe we can create a wrapper for the script that helps it execute the call properly against the un-wrapped binary or something.
Howdy , I created that should fix this issue. Would you be able to try this fix out yourself to see if it works for you?

Discussion:
--set NIX_REDIRECTS ${builtins.concatStringsSep ":" redirects}  --set LOCALE_ARCHIVE "${glibcLocales.out}/lib/locale/locale-archive"  "''${gappsWrapperArgs[@]}" <ins> # We need to replace the ssh-askpass-sublime executable because the default one # will not function properly, in order to work it needs to pass an argv[0] to # the sublime_merge binary, and the built-in version will will try to call the # sublime_merge wrapper script which cannot pass through the original argv[0] to # the sublime_merge binary. Thankfully the ssh-askpass-sublime functionality is # very simple and can be replaced with a simple wrapper script. rm $out/ssh-askpass-sublime makeWrapper $out/.${primaryBinary}-wrapped $out/ssh-askpass-sublime  --argv0 "/ssh-askpass-sublime" </ins> ''; }; in stdenv.mkDerivation (rec {

} {}; sublime-merge-dev = common { <del> buildVersion = "2011"; sha256 = "0r5qqappaiicc4srk08az2vx42m7b6a75yn2ji5pv4w4085hlrzp"; </del> <ins> buildVersion = "2022"; sha256 = "0fhxz6nx24wbspn7vfli3pvfv6fdbd591m619pvivig3scpidj61"; </ins> dev = true; } {}; }