I've got a number of emacs sessions running, all normally. Today I cloned a GIT tree and went to explore the tree with emacs in a text session terminal, and had emacs start using 100% CPU. Emacs didn't respond to anything, but was killable in another session.
Gord -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
