* Replying to a msg in FTSC_PUBLIC ([ADM] FTSC Public Echo)   
      
   Hi! Nicholas,   
      
   On Sat, 01 Dec 12, 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 some   
    NB> sleep. :) I noticed that as well, which seems to be Synchronet   
    NB> forcing it's tear line and origin line in there when the tosser takes   
    NB> care of it.   
      
   This is a situation that I've only recently evolved my SemPoint & GoldEd   
   editors into, in combination with my FastEcho (FE) tosser.  See below for   
   GoldEd.  Keep that Origin line thought (above) in mind for 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)?   
      
   Well, yeah.  These changes are in my GoldEd config file from November 8th...   
    --- 8< ---   
   xxxx USEPID   (no if GoldEd mentioned in tearline, yes otherwise)   
       If disabled then @PID kludge will not be used in your messages.   
   USEPID yes   
      
    Enable this to get a blank tearline and use a PID kludge instead.   
   EMPTYTEARLINE YES   
    --- 8< ---   
      
   Bummer.  I just realised that I started this note in SemPoint.  Here it is   
   from GoldEd, instead.[sfx: kaching! sound]  I've left my Origin set here even   
   though I know I can force it with FE, so, I'll let you toy with that idea.  :)   
      
   Cheers,   
   Paul.   
      
   ... Never argue with the Divine Right of SysOps.   
   --- Paul's Win98SE VirtualBox   
    * Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)