Sven, On 28 December 2008 at 10:06, Sven Joachim wrote: | On 2005-03-12 02:12 +0100, Dirk Eddelbuettel wrote: | | > Package: vm | > Version: 7.19-2 | > Severity: normal | > | > Hi Manoj, | > | > I wish I had a better handle on why/how this happens. I used to read mail in | > vm under xemacs (which worked for years even though you always insisted it | > wasn't supported) but then switched to mutt as my folders got to big. | > | > About maybe two months ago, I switched back to vm, but as it failed to work | > under XEmacs, switched over to GNU Emacs for mail. It is entirely possible | > that some part of the old, grown, convoluted paramters and setting in | > ~/.emacs* and friends have something to do with this bug -- but I am not | > sure how would I could tell or find out. I don't really read or program | > elisp, I merely adapt the configuration based on docs. | > | > Anyway, to cut a long story short, about once a week vm takes emacs down | > hard. This typically happens when a new mail folder is read. | > | > Have you ever come across a bug report like this, and is there something I | > could do ... while I cannot actively trigger the bug. I could enable | > logging. I tend to remove the (massive) core file. | > | > This is on always current testing, and I am mostly filing this bug to give | > us a chance to address this before the release. If you find the bug report | > too intagible and feel you need to close it outright, I would not be too | > shocked -- though obviously not please either. As I said, I wish I had more | > pointers. | | I'm currently triaging old bugs in emacs21, to which this bug has been | reassigned. Do you still see these crashes in emacs21 and/or emacs22?
No, I have not seen this in quite some time. In the 3 1/2 years since I filed this, vm (and emacs) have changed a little bit so I think this can be closed. For what it is worth, I currently use the emacs-snapshot package. Thanks for doing the triage. Dirk -- Three out of two people have difficulties with fractions. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
