Re: [BorCVS-support] (no subject)

[Thomas B. <th...@bl...>]

Hello!

Well, BorCVS currently captures all output (STDOUT) from the CVS 
subprocess and displays it in it's own window. Theoretically it would be 
possible to feed in some data (passwords, etc) via STDIN, but I don't know 
any way to determine _when_ an appcation is waiting form STDIN input, so 
it won't work in practice. If anybody has an idea how this could work, 
please tell me. Also, the WinCVS way would be nice to be implemented, so 
everyone's invited to do so ;-)
__
/homas

On 24 Jun 2002 at 20:57, Patrick Dunford wrote:

> Ok I set up CVS_RSH=SSH.
> For WinCVS I already have HOME=F:\SSH and PATH=%PATH%;F:\SSH
> 
> Then I call up cvs with
> C:\>"F:\Program Files\GNU\WinCvs 1.2\cvs.exe" -d
> :ext:pdu...@cv...:/cvsroot/dunfordsoft
> checkout -P
> autoexec
> 
> Which I have done by setting CVSROOT in BorCVS to
> :ext:pdu...@cv...:/cvsroot/dunfordsoft
> 
> But the thing is, when WinCVS calls SSH it brings it up in a separate
> command prompt window and asks for the password. You type your password
> into the command prompt window and off it goes.
> 
> Whereas BorCVS brings up the password request in its own CVS output window
> and won't receive input in this window.
> 
> WinCVS is able to separate the CVS output from input requests as far as SSH
> goes, and works perfectly well with SSH.
> 
> By the way I am running BorCVS on Windows 95 on Delphi 5 standard - a
> suitable enough platform for OSS development methinks.

        _\\|//_
        ///|\\\
----oOO---(_)---OOo------------------------<http://www.bleier.at>----------

"The amount of sleep needed by the average person is ten minutes more."