From: fred.holmes@mix.cpcug.org (FRED HOLMES)
Joe Souza said:
JS> An editor does not have to be really fast.  Most of the time
JS> it's just sitting there in a loop, waiting for user input.
JS> I'm not sure we'll see a noticeable speed difference when
JS> compared with TSE/32.
TSE is more than just an editor, and its speed is very important.
For example, using TSE's macro language, I do a keyword (and
other types of) search on a daily ASCII file of the Commerce
Business Daily (where synopses of U. S. Government offers to
purchase goods and services are posted), clipping items that may
be of interest and arranging them into categories.  Speed in
doing this is definitely important.  TSE is not only better
(because of its extensive macro language) than anything else I've
come across, it is also much faster.
I do similar searches of the Congressional Record.  On a busy day,
the CR file is a couple of megabytes.  To search a month's worth,
I'm searching 20 Megs or more.  The regular expressions are
essential, but are much slower than simple searches.  I don't
know how to categorize the problem precisely, but when Sammy
speeds up the regular expression searches, I'll be very happy.
---
---------------