Re: interactive hg (mercurial) using ssh is getting authentication failures to sourceforge
Greetings, Ernie Rael! At the end of this post, there is experimental evidence that the ssh is disasociated from the tty in the when spawned by hg. NOTE: hg is a Win7 command, not compiled with the cygwin dll. Don't you see anything suspicious here? -- WBR, Andrey Repin (anrdae...@yandex.ru) 12.05.2014, 15:20 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: interactive hg (mercurial) using ssh is getting authentication failures to sourceforge
On 5/12/2014 4:20 AM, Andrey Repin wrote: Greetings, Ernie Rael! At the end of this post, there is experimental evidence that the ssh is disasociated from the tty in the when spawned by hg. NOTE: hg is a Win7 command, not compiled with the cygwin dll. Don't you see anything suspicious here? Right you are. After I posted, I realized I hadn't clearly stated my questions. This could be something about my setup, but... I've only just joined this mailing list; I don't have an historical perspective. Is this expected behavior? If so, any idea what changed over the last 6 - 9 months? Was this a conscious change in behavior? I'd been using this setup for years; the old behavior, which gives a higher degree of interoperability (at least in this case), is certainly natural. If the Win program didn't do anything explicit to disassociate from the tty, why shouldn't it work? Does windows have a concept of controlling tty? Is there something mercurial/python could, as a native app, that would get this to work? I know little about windows' internals. I understand that even though it used to work, that it may have been a 'fortunate accident. -ernie -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: interactive hg (mercurial) using ssh is getting authentication failures to sourceforge
On 05/12/2014 09:21 AM, Ernie Rael wrote: On 5/12/2014 4:20 AM, Andrey Repin wrote: Greetings, Ernie Rael! At the end of this post, there is experimental evidence that the ssh is disasociated from the tty in the when spawned by hg. NOTE: hg is a Win7 command, not compiled with the cygwin dll. Don't you see anything suspicious here? Right you are. After I posted, I realized I hadn't clearly stated my questions. This could be something about my setup, but... I've only just joined this mailing list; I don't have an historical perspective. Is this expected behavior? If so, any idea what changed over the last 6 - 9 months? Was this a conscious change in behavior? I'd been using this setup for years; the old behavior, which gives a higher degree of interoperability (at least in this case), is certainly natural. If the Win program didn't do anything explicit to disassociate from the tty, why shouldn't it work? Does windows have a concept of controlling tty? Is there something mercurial/python could, as a native app, that would get this to work? I know little about windows' internals. I understand that even though it used to work, that it may have been a 'fortunate accident. I believe the point that Andrey's making is that 'hg' being a Windows native app is significant in your workflow. When you wander into the area that involves ttys, there are more restrictions on what will work. Windows doesn't have ttys and Cygwin emulates them. Mixing tools which don't understand ttys with those that emulate them is not a recipe for success, even if things work OK in some situations. Your simplest route to a solution may be to just use the Cygwin version of 'hg'. -- Larry _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
