Neil Hodgson wrote:
Robert Roessler:
I can not confirm this on WinXP with 1.70 - what version are you using?
This occurs when a current working directory of the SciTE process is
the directory being deleted. Its been bought up before and it may be
possible to fix if anyone has the time to research how to find a safe
'parking directory' for SciTE on Windows bearing in mind that on Windows
each process has one current working directory per disk.
Like I said, I can not confirm this on XP with 1.70 - I set this up a
number of times in different ways, but was unable to ever get any
error... at least based on the information presented. Is just reading
the files not enough? Must they be written by SciTE during that
session to "lock" their containing directories?
Ah - this can be done if using the Open dialog... something I never
do, since I always just drag files from an Explorer window. :)
A few observations from using Process Explorer:
1) the handle that is held is to a *File*, not a *Directory* - even
though the listed item is the path of the folder (odd but not germane)
2) the ONLY handle held is to the LAST directory a file was loaded
from using the Open dialog - there are NO handles held for the
directories of the previously opened files
Given the evidence, it appears like there really is just ONE "current
working directory" per process (as expected), and that any illusion of
multiple ones is caused by something like a command shell.
This suggests that SciTE could just always do something like switch
its current working directory to, say, the one the exe lives in after
any file op that may have changed it (like using the Open dialog)...
maintaining friendly behaviors like remembering the previous Open
dialog dir can be done explicitly (which it may be doing already).
Robert Roessler
[EMAIL PROTECTED]
http://www.rftp.com
_______________________________________________
Scintilla-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scintilla-interest
