[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [TSVN] [bug] unable to connect with wathever plink used

From: Valik <vampire.valik.ml_at_gmail.com>
Date: 2005-09-15 22:51:00 CEST

Stefan Küng wrote:
>> So I have some suggestions :
>> - display a message when tortoiseplink failed for whatever reason ;
> As mentioned above, that's not possible without almost completely
> rewriting Plink. TortoisePlink is just a slight modification of Plink,
> and we like to keep it that way so we can keep up with new versions of
> Plink without too much work.
> Stefan

Every time you say that I wonder: Why don't you just capture the output
by replacing the stdout/stderr handles? If Plink is a CUI application
then you should be able to change a DWORD in the PE header
(IMAGE_NT_HEADERS::OptionalHeader.Subsystem) to make it a GUI
application (Prevents the console from appearing but everything else
seems to work okay, YMMV, though as I've not thoroughly tested this
concept). Then just replace the stdout/stderr handles when you call
CreateProcess() and you get the best of both world's without having to
maintain anything.

I don't use Plink/TortoisePlink so I don't really care what you do, but
I do wonder why you keep saying it can't be done. Does Plink not write
it's data to the stdout/stderr streams? If not, then I completely
understand why you don't do it. But if it does write to those streams,
then I don't see any good reason not to catch those messages.

- Valik
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Sep 15 22:53:19 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.