Hi Paul,   
      
   On Mon 2039-Mar-21 20:04, Paul Quinn (3:640/384) wrote to Richard Webb:   
      
   PQ> Oh man, your ears must have been burning as I recently started   
   PQ> browsing some nodelist search software (but haven't tried any yet).   
      
   Nope, but glad to hear it.  I've been using your little   
   creation quite a bit for that application in fact.  I've got one version of it   
   that just displays results to the screen,   
   another that dumps results to a text file, which can then be sent as a   
   message, etc.   
      
   PQ> It looks like you're keeping tabs on my batch file website   
   PQ> doo-hickey.  :)  Yeah, I had to rewvert to using my Tic2Dir batch   
   PQ> file when the old TICK 2.10 dropped dead, after I cloned the whole   
   PQ> Fido PC to a VirtualBox 'appliance'.  (TICK didn't like the new CPU   
   PQ> driving the host Ubuntu system.)  I don't have any downlinks and   
   PQ> only have a handful of file areas to worry about in any case, so   
   PQ> Tic2Dir seemed ideal.   
      
   Nope, hadn't been lookin' at your web, but looked at tic2dir when I first   
   joined fido again, and some of your code in it   
   for another application.   
      
   PQ> I'm also half-heartedly hunting down a replacement for Qnode as it   
   PQ> dropped dead following the cloning.  It's not an absolute   
   PQ> requirement as I no longer run BinkleyTerm but I do like to keep   
   PQ> things 'as they were'... because.    
      
   Iirc qnode does v7 nodelist.  I use tbbsnc for that,   
   essentially xlaxnode without the cripple, written for tbbs   
   sysops.   
   I've also got fastlist around here but never really set it   
   up, thought about it a couple of times, but tbbsnc works,   
   and found something else to do that break what was already   
   working.  I should have tried fastlst back in the day though but never did.   
      
    RW> My latest project is some msg area analysis stuff.  I'll   
    RW> drop in in a couple weeks if you're interested and give you   
    RW> a look see at some of it. Hmmm, for that matter might be back with    
    RW> some questions for the gurus around here.   
      
   PQ> Okay.  So long as it's simple stuff I might be able to help but I'm   
   PQ> always on the lookout for a guru too, as I really really prefer to   
   PQ> lurk.    
      
   DItto here, I learn more that way.  sUre miss seeing some of the old guys   
   around here, Vernon, etc.   
      
    RW> Btw did you ever get that routine you were working on for   
    RW> busting email digests to post as fido msgs working the way   
    RW> you wanted?   
      
   PQ> Ermm, I shelved the whole idea.  My head hurt too much trying to   
   PQ> fathom the problem.  The traffic is like about 1-2 messages per   
   PQ> night and most of those are solved by hitting [Next] anyhow.  Really   
   PQ> 'must read' newsgroup garbage.    
      
   Understand that.  Still think it was a doable thing though.   
   I sort of played with something similar for a little   
   project, related to my work with the boats.  WHen my system   
   does its little weekly journals detailing who's been using   
   our communications services a buddy sends me all the dope   
   from other databanks on vessels that I don't have any info   
   for but the call sign, maybe the radio op's name as well.   
   HE gives me the vessel's description, how many people   
   aboard, vessel's marine call sign, comms capabilities,   
   whether or not the cruisers have their own web site or are   
   doing position spots via other means to the internet.   
   Often there are more than one of these per message he sends   
   me.   
      
   So what I did is rigged up a way to let the automation do   
   its thing after an edit.   
   I want the amateur call sign of each on every line of the   
   output, so that a search for that call sign returns *all*   
   the data we have.   
      
   So, the first line of each entry he sends me gets the   
   keyword "callsign:" then the amateur call sign.  tHen we   
   have keywords "operator:" "vessel:" and "heardlist"   
   THose lines get special treatment.   
      
   Each entry is marked by "endboat" on a line by itself.   
      
   So, after I see one of Rex's messages to me with such info I save it as   
   rexboats.txt from timed, which is then brought up in my text editor, along   
   with another text file which jogs   
   my memory as to the keywords.   
      
   WHen the editing of the file is done, (automation removes a   
   lot of the mime junk) We then let automation run again.  IF, for example, Rex   
   sent me info on 5 different vessels there   
   should be 5 "callsign:" entries in the text file, and five   
   "endboat" markers.  IF not , processing aborts and it sends   
   me a message.   
      
   If all's copacetic, 5 apparent records, 5 end of record   
   marks, we stuff "callsign:" into an environment variable   
   with HOrst's nset, dump all lines through next "endboat" to   
   a file with the call sign on each line with listmod, dump   
   that remaining file to be processed out to another file   
   which is renamed to the master input filename, lather rinse   
   repeat.  Was thinking you could probably do something   
   similar with your digest buster.   
      
      
   Regards,   
              Richard   
   --- timEd 1.10.y2k+   
    * Origin:  (1:116/901)