Subj : msg test
To   : Richard Webb
From : Mike Tripp
Date : Thu Sep 24 2009 09:24 am

Hello Richard!

23 Sep 09 23:32, Richard Webb wrote to Kevin Klement:

 RW> YOu could use backbone.dst and create the batch file
 RW> automagically using HORst's listmod, i.e.

Have seen you tout LISTMOD quite a bit.  Sounds like a decent alternative to my 
routine of inserting specific characters in prepend and append locations using 
the editor or commandline search-n-replace and then replacing the characters 
with the appropriate strings.

 RW> SO, every time Ross sends out a backbone.dst you could do
 RW> this automatically and only nuke the areas contained in it.

My ritual here is a bit more elaborate also.  I prefer to evaluate the history 
in the area first before deciding whether to retain it as an archive in spite 
of it's backbone status, or dump it.  So I usually

- make a backup copy of SQUISH.CFG if I'm expecting a small set of changes or 
SEAL LIST to make a backup .NA of what's already locally configured if I'm 
expecting a bunch

- SEAL DESCRIBE against the current .NA with the -f (forced) switch

- examine SQUISH.CFG to see which areas lost their descriptions due to not 
being found in current .NA

- recover descriptions for keepers using backup SQUISH.CFG and editor or backup 
..NA with SEAL DESCRIBE (not forced).

- SEAL DELETE the ones to dump.

I =try= to remember to delete my uplink from the link list for the areas that 
are dropped from the .NA but archived by me during the description recovery 
step also, so that it looks like a local echo rather than a backbone echo.  All 
the folks running in "auto-create" mode is what keeps the dead areas from truly 
dying after they're dropped from the .NA.

..\\ike

--- GoldED 2.50+
 * Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

.