Grant Shoshin Shangreaux <[email protected]> writes: > sometimes i'd get a type error, but then emacs would go into a state > were my cpu was pegging at 100% and fans turned on high. i could C-g to > break out of it. here's the stack trace when quitting: > > Debugger entered--Lisp error: (quit) > emms-browser-level-at-point() > emms-browser-find-top-level() > emms-browser-mark-entry() > emms-browser-mark-and-collapse() > emms-browser-expand-to-level-2() > funcall-interactively(emms-browser-expand-to-level-2) > call-interactively(emms-browser-expand-to-level-2 nil nil) > command-execute(emms-browser-expand-to-level-2)
This looks like the same bug that Keno Goertz reported recently. It would be good to have it fixed. > happy to work on it when i get a chance. just waiting on my boss to sign > off on my FSF assignment Great! Petteri
