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 351 of 2,690   
   Nicholas Boel to Paul Quinn   
   FTS-5000.003   
   01 Dec 12 22:10:21   
   
   Hello Paul.   
      
   02 Dec 12 09:07, you wrote to me:   
      
    PQ>>> V-e-r-y nice, Nick.  Looks nice on this side of your monitor.   
    PQ>>> Maybe you ought not set the Origin in GoldEd? ...   
      
    NB>> That was my last post of the night, as it was 4am and I needed   
    NB>> some sleep. :) I noticed that as well, which seems to be   
    NB>> Synchronet forcing it's tear line and origin line in there when   
    NB>> the tosser takes care of it.   
      
    PQ> This is a situation that I've only recently evolved my SemPoint &   
    PQ> GoldEd editors into, in combination with my FastEcho (FE) tosser.  See   
    PQ> below for GoldEd.  Keep that Origin line thought (above) in mind for   
    PQ> yours.   
      
    NB>> Is there a clean-cut option to disable these in Golded (I   
    NB>> also noticed if you _don't_ use the tear line in Golded, it will   
    NB>> create a PID kludge with the Golded version information, so that   
    NB>> would be nice anyways)?   
      
    PQ> Well, yeah.  These changes are in my GoldEd config file from November   
    PQ> 8th... --- 8< --- ;xxxx USEPID   (no if GoldEd mentioned in   
    PQ> tearline, yes otherwise) ;    If disabled then @PID kludge will not be   
    PQ> used in your messages. USEPID yes   
      
    PQ> ; Enable this to get a blank tearline and use a PID kludge instead.   
    PQ> EMPTYTEARLINE YES   
    PQ>  --- 8< ---   
      
    PQ> Bummer.  I just realised that I started this note in SemPoint.  Here   
    PQ> it is from GoldEd, instead.[sfx: kaching! sound]  I've left my Origin   
    PQ> set here even though I know I can force it with FE, so, I'll let you   
    PQ> toy with that idea.  :)   
      
   No worries. It looks like I'm getting everything fixed up as I continue   
   reading the docs.   
      
   ctrlinfoecho no   
   ctrlinfoemail no   
   ctrlinfonews no   
   ctrlinfolocal no   
   emptytearline yes   
      
   Seems to do the trick! Now that that's settled. I'm going to tinker with   
   charsets and see if I can get away from this CP437 stuff. Thanks for the tips!   
      
   Nicholas   
      
   --- SBBSecho 2.20-Linux   
    * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)   

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


(c) 1994,  bbs@darkrealms.ca