home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   GOLDED      GoldED Public Release discussion.      2,690 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 2,185 of 2,690   
   Vitaliy Aksyonov to Nicholas Boel   
   Re: Latest sources..   
   20 Feb 24 07:04:00   
   
   REPLY: 1:154/10 65d3ea40   
   MSGID: 1:104/117 65d4b4eb   
   CHRS: US-ASCII 2   
   TZUTC: -0700   
   TID: hpt/lnx 1.9 2022-07-03   
   Hello Nicholas.   
      
   19 Feb 24 17:54, you wrote to me:   
      
    VA>> Then most probably it has 'soft CR'. You may dump message hex   
    VA>> codes with 'I'.   
      
    NB> I assume I'm looking for 8D somewhere? If so, there are none in the   
    NB> entire message.   
      
   Yep. Looks like that message doesn't have soft CRs.   
      
    NB> I did notice a question mark in the message body:   
      
    NB> 00B0   C4 C4 C4 C4  C4 BF 20 C4  C4 C4 C4 C4  C4 C4 C4 C4    ?   
      
    NB> But that's about it as far as anomolies.   
      
   Code 20 is a space. So wrapping caused by that.   
      
   Also check if you have DispMargin parameter in your config. If you do -   
   comment it out or remove. Then GoldEd will use all window width.   
      
    VA>> If you just want to use specific commit, then use git checkout.   
    VA>> If you want to do binary search for broken commit - use git   
    VA>> bisect interactively. Here's a tutorial, how to use it:   
      
    NB> I used checkout to get the specific commit you asked me to grab   
    NB> (372220588c6f17cd3f709dcb721a9144169d988c), and it is indeed exactly   
    NB> how the latest version is. So you were right.   
      
   You said that before you started to experiment - all worked fine. Have you   
   used same compiler? Now I suspect that issue caused by something in your   
   setup. Because it's quite opposite from others have.   
      
    VA>> And that's is very strange. I'd not be surprised if it was broken   
    VA>> when I made first change (which was reverted by last commit), but   
    VA>> looks like it worked fine.   
      
    NB> It did not. Whatever first change you made actually kind of helped me,   
    NB> I suppose. Hopefully this helps narrow things down better and we can   
    NB> figure out what's going on.   
      
   That's why would be interesting to use bisect from 372220588c6f1   
   cd3f709dcb721a9144169d988c to master and find specific commit which made it   
   bad in your specific case.   
      
   Vitaliy   
      
   --- GoldED+/LNX 1.1.5-b20231030   
    * Origin: Aurora, Colorado (1:104/117)   
   SEEN-BY: 15/0 18/200 50/109 90/1 104/117 105/81 106/201 128/260 129/305   
   SEEN-BY: 135/225 153/7715 218/700 226/30 227/114 229/110 112 113 206   
   SEEN-BY: 229/307 317 400 426 428 470 664 700 266/512 280/464 5555   
   SEEN-BY: 282/1038 291/111 292/854 301/1 320/219 322/757 342/200 396/45   
   SEEN-BY: 460/16 58 256 1124 5858 463/68 467/888 633/280 712/848 3634/12   
   SEEN-BY: 5000/111 5001/100 5005/49 5015/46 5020/828 846 1042 4441   
   SEEN-BY: 5030/49 5054/8 30 5061/133 5075/128 5083/444 5090/958   
   PATH: 104/117 5020/1042 460/58 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca