Matija Grabnar 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 UNSUBSC
Package: emacs
Version: 23.4+1-2
Followup-For: Bug #91
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.
I have two amd64 machines, they both get exactly the s
2 matches
Mail list logo