Friedrich Delgado <frie...@nomaden.org> writes: > I'm switching back to emacs-lucid now, since the crashes have become > quite frequent. Since this bug exists in functionality I don't care > about (gtk), I simply switch to a non-buggy package. > > Sorry if you don't enough information to track the bug down, but if > I'm the only one having this problem, it's probably not that > important, as long as you don't suddenly decide to deprecate the > emacs-lucid package ;-}
That's very unlikely since I use it myself. I switched back to the lucid package a while ago because I got tired of having emacs lock up and peg the cpu any time you were unexpectedly disconnected from a --daemon session (i.e. if you lose the connection from a remote emacsclient buffer). When I investigated (IIRC I discussed it upstream), it looked like there was a fundamental problem in the way GTK+ handles X connections, and there was nothing emacs could do about it. Since I didn't care *at all* about the GTK+ interface I dropped it. > Feel free to close/wontfix/whatever. I suspect there's a real bug here, so we'll leave it open. I imagine we (or upstream) will track it down eventually. Thanks for the help -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
