Re: Re: getting rid of cvsgui protocol

Jens,

>Yes, it's on my list - basically, cvsnt already builds on Mac OS, but I
>need to transfer the modifications for resource fork management before
>it can really be used on the Mac...

I am sure it's worth the effort, because CVSNT is fully compatible with
classic CVS servers and it offers a lot of new features apart from cvsgui
protocol ;)

I am sure Tony will gladly incorporate any needed changes to make CVSNT
building and working on Mac.

>However, I doubt that cvsnt actually solves the problem of e.g. ssh
>reporting errors/warnings/information to stdout/stderr, since all cvsnt
>does it to #define printf cvs_printf and thus it conly catches printfs
>_compiled_ into the cvsnt code. (I'd be glad if you prove me wrong here
>;-)

I am not sure whether you are going to see these if you simply intercept
pipes either. In WinCvs in case of problems with ssh people are advised to
select the "Show TTY" checkbox which is causing the console to show up and
allows to read any ssh messages as well as type the text back when the
passwords are requested by ssh.

>One might be able to work around this issue by calling setvbuf on the
>stdout pipe - not sure whether setvbuf works on pipes or not, though...

setvbuf is not guaranteed to provide line ending buffer flushing on all
platforms and according to MSDN it doesn't work on Windows. Which means that
all we've got is the protocol ;)

>BTW: where do ssh messages end up in WinCvs? Do you get them in the
>WinCvs log, or do they end up in the shell output window?

It shows after you enable "TTY" checkbox, in a separate console window.

Best Regards,
Jerzy

 

Yahoo! Groups Links

To visit your group on the web, go to:
 http://groups.yahoo.com/group/cvsgui-dev/

To unsubscribe from this group, send an email to:
 [email protected]

Your use of Yahoo! Groups is subject to:
 http://docs.yahoo.com/info/terms/