Matija Grabnar <[email protected]> wrote: > I can confirm that I am seeing this problem, too. > emacs -nw blocks, eating 100% CPU and not accepting any > input. The only way to get out of it is to kill emacs from > another session.
It's the same here when I invoke Emacs from a virtual console. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
