On Feb 16 96 17:26, Jerry Schwartz wrote to Bill Bond:

BB>> So if it wrote it on the fly, automatically, that would be ok?

JS> What's the down side?  How harmful are duplicate entries in 
JS> echotoss.log?

I started with an option to write it after each message.  Then I realized
that it would end up writing to ten times if you wrote ten messages in the
same echo.  I ended up with Msgedsq writing it after each area change, as
you mentioned earlier.  The downside is that it will still write dupe
entries if you leave an area then go back and leave it again.  I did end up
making it an option so that you could either use the existing behavior or
the new behavior.   If the new option is enabled then Msgedsq doesn't write
out an echotoss.log at exit.

Dupes are a fairly minor problem, it just causes the tosser to scan that
area twice, or more.


BB>> Groan :)

JS> Just say no.  What he really wants is a full msged.cfg editor 
JS> built in; not a bad idea, but a fair size job.

NO!

:)

Bill

--- MsgedSQB/2 3.30.01

SDŽ¯ė_