I'm experiencing a strange bug which I wonder if anyone else
on the "experts" list has seen or can verify and report on:
To tickle the bug:
cp /usr/share/dict/words (or any other large text file) to /tmp
The file should contain a large number of lines, say, greater than 50000.
Now edit /tmp/words with emacs.
Now delete the contents of the buffer.
You can do this in a hundred different ways.
The fastest is, perhaps:
C-x h C-w
which "marks" the whole buffer as the current "region" and
then "kills" it.
When I do this (under a cleanly installed Mdk 8.1 using KDE)
emacs just locks up. If I hit C-g, it beeps and 20-30 seconds later
I get:
Time out waiting for property-notify event
in the emacs "echo area" and emacs remains locked up. Must kill
it from another window.
Just yesterday I discovered that my colleague's emacs does the same
thing under Mdk 7.2.
But other's have not been able to reproduce the problem. I'm stumped
and it is more than a little annoying since 98% of my life on the
computer is spent w/in emacs.
I've been able to discover that the bug does _not_ occur if you use
`emacs -nw' in, say, an "xterm", or if you use the emacs from a
v-console (say, alt-ctl-F2). It's only when emacs is allowed to paint
its own window (or "frame" in emasc parlance) that it occurs.
Dean
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
