Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Hello Tony,
tmh at nodomain.org (Tony Hoyle) writes:
> If it only happens with Visual SlickEdit open it's possible that
> it's holding the files open that are being edited - this will
> prevent cvs from manipulating the files. In that case I'd expect
> there to be an option in the IDE to close them.
Thanks again for the hint. I looked into the VSlick settings and found
two related options ("File locking" and "Auto read-only"). The latter
because of the fact that it works with CVSNT build 62, and build 63
introduced the PRESERVE_PERMISSIONS-feature. I'll get a developer to
test these settings. On my machine I can't reproduce the problem in
whatever setting I try. Anyway, I'll tell them that the IDE must been
closed (Hope they understand... ;-)
But now for CVSNT: Isn't there a way of exiting cleanly in a situation
like this? I have no good understanding of Win32 file i/o and don't
know what kind of file open the VSlick editor uses. When looking at
the CVSNT sources I think that every i/o error is catched and should
produce an error. I don't understand how it can stop responding like
it does.
Do you have an idea of what happens?
Thanks again for the fast response.
bye,
OK.