labath wrote: > * I can append to the file from Python (mode="a") > > * I can delete the file from Python (what the current test is doing) > > * I cannot delete the file from File Explorer => says lldb.exe is using the > file > > * I cannot overwrite the file from Python (mode="w") > > * I cannot overwrite/save the file from Notepad++ > > * I can overwrite/save the file from vi.
Well, that's... interesting. Thanks for gathering these. I suspect that this is due to different strategies for saving a file. I know of basically two: you either delete the file and create a new one in its place (if you want a backup you can rename instead of deleting), or you overwrite the file in place (and make a copy if you want a backup). In vim, this is controlled by the `backupcopy` setting so it would be interesting (but not really necessary) to see if this affects vim's ability to save the file. With this in mind, deleting the file *is* representative of an editor wanting to save the file using the deletion strategy, but I still think it's not our goal here to ensure the editor *cannot* save the file if the setting is `true`. https://github.com/llvm/llvm-project/pull/111237 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
