That's too bad. I run with most of the goodies turned on with my
poor little 333Mhz processor, and I don't have this problem.
One thing you can try is "toggle-debug-on-quit", and when you feel a
pause, quick hit C-g to see what it is waiting for. That, at least,
will give us a clue where to start looking.
>>> Jan Sacharuk <jan@...> seems to think that:
>On Tue, 06 May 2003 10:15:46 -0600, Jan Sacharuk <jan@...> wrote:
>So, nobody has any further advice to tell me what I can do to speed
>anything up? I'm personally inclined to blame WinXP a fair amount for this,
>but these performance issues are really quite bad. I don't want to turn
>EVERYTHING off all together, but it's looking more and more like I'll have
>to. Getting a 5 second delay while trying to move forward through some code
>or modify a variable is really entirely unacceptable.
>> Incidentally, it didn't help. I still have odd hang-ups when trying to
>> work. While it's sort of a shame, I'd sort of like to be able to turn off
>> the little tips that show the syntactic construct that you're working in
>> (if, while, whatever) or the class or method that you're currently
>> editing in the command mini-buffer (or whatever it's properly called.)
Eric Ludlam: zappo@..., eric@...
Home: http://www.ludlam.net Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net GNU: http://www.gnu.org