Re: Kat / RDS: File locking
- Posted by Pete Lomax <petelomax at blueyonder.co.uk> Sep 23, 2004
- 404 views
On Thu, 23 Sep 2004 02:04:46 -0700, Brian Broker <guest at RapidEuphoria.com> wrote: >Just thought I'd pipe in about the file locking thing. I've been using >ConText for editing my programs (with hotkey/one-button execution). When >I'm debugging I'll run the program from the editor, read the run-time error >without pressing Enter to continue, fix the error and save the file. But >sometimes the file saves just fine (even with the previous instance still >waiting for my 'Enter'), and other times it refuses to save the file >(presumably locked by the interpreter) until I close the previously-errored >session. > >I'd say it's about 50/50 whether I can save it while the errored interpreter >was waiting for my key press to end. > >I have no idea if this is related to Kat's issues but thought it might be >relevant enough to mention. Might even be a ConText issue... > I can understand an editor not wanting to save a file it thinks another application is reading. I have suffered this in Code Genie and Crimson, but never in MEditor. If anything, I've occasionally wanted MEditor to detect this as well, but the disadvantages it would bring have so far prevented me from even investigating how it would be done. Occasionally, when I have a file open in MEditor, my zip program (presumably written in C) refuses to _read_ that file until I close it in MEditor. 49 out of 50 times it has no problem. That I find a bit strange, Pete