On Fri, 3 Aug 2001, Charles G. Waldman stipulated:
Maybe I'm spoiled by access to fast hardware, and maybe I am not
being
sensitive enough to the needs of users who do not have such machines,
but it seems like the way to "fix" lazy-shot is with "rm".
Fast hardware doesn't help. I use lazy-lock because I use an extremely
heavy-duty C and C++ fontification regexp by Chris Holt, and it takes
more than half an hour to fontify e.g. `src/eval.c'. I'm not willing to
wait half an hour, or to give up good fontification (and this one
follows the language grammar quite closely and so fontification looks
lovely, with the downside that this makes it *slow*.)
Bigger regexps can make the fontification process slower faster than
fast hardware can make it faster; we need a lazy locking package to
cater for that.
(Another (obvious) reason: if you remove one of them, you'll annoy
people who're using the one you remove. I thought XEmacs kept old
features around in case they were useful, viz extents versus text
properties, or the multiple packages to compress and encrypt buffers and
mail? ;) )
--
`It's all about bossing computers around. Users have to say "please".
Programmers get to say "do what I want NOW or the hard disk gets it".'
-- Richard Heathfield on the nature of programming