You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "mbeckerle (via GitHub)" <gi...@apache.org> on 2023/04/27 16:39:48 UTC

[GitHub] [daffodil-vscode] mbeckerle commented on issue #576: Handle changes made to an edited file done outside the editor instance

mbeckerle commented on issue #576:
URL: https://github.com/apache/daffodil-vscode/issues/576#issuecomment-1526012802

   One alternative is locking the file somehow so concurrent edits aren't allowed at the system level. 
   (e.g., see https://www.baeldung.com/linux/file-locking)
   
   To me that's very preferable to blindly copying the file. I can always do the copy myself. There is complexity to this having to do with avoiding leaving things locked in presence of failures, etc. 
   
   Detecting a concurrent edit dynamically (every time omegaEdit touches the file, verify that modify time has not changed first, and if it has offering options) and then offering to save to a different location is another approach. That enables lazy copying, which is again very preferable to proactive copying overhead. 
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@daffodil.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org