MSGID: 1:317/3 6f3fd3a4   
   REPLY: 1:129/215 d5967e8b   
   TZUTC: -0700   
   TID: hpt/lnx 1.9.0-cur 2019-01-08   
   On 28 Nov 2021, 10:12a, g00r00 said the following...   
       
    g0> You should update but I think they are probably unrelated.  In the case   
      
   I've updated my test system here to 2021/11/24, but haven't had a lot of time   
   to do much testing...   
      
    g0> of the 'conflicted' filenaming, there is nothing in Mystic that does any   
    g0> sort of 'conflicted' file renaming so is coming from your OS or other   
    g0> software via editors or during replication, etc.  To make sure my brain   
      
   Usually, what I'll do, is have a terminal window, or two, open and running   
   mystic -l. These are usually open while I'm working on an MPL, but they would   
   not be actively running them.   
      
   I'll then have Geany open on the other monitor, with the MPS file. I have a   
   hotkey set up in Geany to run MPLC on that MPS file.   
      
   Then I'll run the MPL from one of the terminal windows for testing.   
      
    g0> isn't completely spacing out I searched the source code for the word   
    g0> 'conflict' but the only mention of it is the 'File Conflicts' setting   
    g0> for BINKP servers.   
      
   Thank you for checking. :)   
      
    g0> Can you provide more specifics about which files are being renamed to   
    g0> filename[conflicted].ext?  If you are trying to edit MPL while   
      
   I have deleted a lot of the conflicted files, but here is a list of ones still   
   on my test system:   
   history [conflicted].dat   
   mystic [conflicted].dat   
   mystic [conflicted 2].dat   
   mystic [conflicted 3].dat   
   mystic [conflicted 4].dat   
   nodeinfo (conflicted).now   
   nodeinfo (conflicted 1).now   
   nodeinfo (conflicted 2).now   
   nodeinfo [conflicted 2].now   
   nodeinfo [conflicted].now   
   rcslogin [conflicted 7].mpx   
   users [conflicted 6].dat   
   winter [conflicted].mps   
   winter [conflicted].mpx   
      
   I have had some of the .log files show the 'conflicted' as well.   
      
    g0> running/compiling it, maybe the OS is doing it or the editor you are   
    g0> using to edit the source file is doing it when it is not able to save?   
      
   I do have Geany set up to auto-save every 5 minutes, but I'll save before I   
   compile it. Also, I'm not sure why there would be any issues with the   
   mystic.dat, or even nodeinfo.now files, as I don't mess with those files at   
   all.   
      
   I have to head into work now, but have tomorrow off. I'll see if I can do some   
   investigating, and run some tests with the new pre-alpha as well.   
      
   Thank you for taking a look at this. It's not a major problem. It's more of an   
   inconvenience. :)   
      
      
   ---   
      
   Black Panther(RCS)   
   aka Dan Richter   
   Castle Rock BBS   
   telnet://bbs.castlerockbbs.com   
   http://www.castlerockbbs.com   
   http://github.com/DRPanther   
   The sparrows are flying again...   
      
   ... Press any key to continue or any other key to quit...   
      
   --- Mystic BBS v1.12 A47 2021/09/07 (Linux/64)   
    * Origin: Castle Rock BBS - bbs.castlerockbbs.com (1:317/3)   
   SEEN-BY: 1/123 90/1 105/81 114/705 120/340 123/120 131 129/305 226/30   
   SEEN-BY: 227/114 229/101 424 426 428 452 550 664 700 240/5832 249/206   
   SEEN-BY: 249/307 317 400 282/1038 292/854 298/25 301/1 305/3 317/3   
   SEEN-BY: 322/757 342/200 633/280   
   PATH: 317/3 229/426