From: nospam.g00r00@f215.n129.z1.fidonet.org   
      
    BP> 132x37) After noticing the issue with the 'conflicted' files, I did see   
      
    BP> This is running a slightly older pre-alpha version of Mystic,   
    BP> (2021/08/29) so maybe I really need to update... ;) I'm wondering if it   
    BP> might be related to the issue that someone else had with being dropped   
    BP> to a command prompt when running locally...   
      
   You should update but I think they are probably unrelated.  In the case of the   
   'conflicted' filenaming, there is nothing in Mystic that does any sort of   
   'conflicted' file renaming so is coming from your OS or other software via   
   editors or during replication, etc.  To make sure my brain isn't completely   
   spacing out I searched the source code for the word 'conflict' but the only   
   mention of it is the 'File Conflicts' setting for BINKP servers.   
      
   Can you provide more specifics about which files are being renamed to   
   filename[conflicted].ext?  If you are trying to edit MPL while   
   running/compiling it, maybe the OS is doing it or the editor you are using to   
   edit the source file is doing it when it is not able to save?   
      
   ... Evil triumphs when good people do nothing. - Einstein   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)