"Benj. Mako Hill" <[EMAIL PROTECTED]> writes: > > Rich Walker: Thanks for the bug, I'm marking this an upstream and bug > and pointing it out to Mairix's author and my upstream. Thanks for the > but report and I apologize for letting it slip through the cracks like > this. You can try out Mairix 0.20 which was uploaded a few days ago and > let me know what you think -- about this bug and others you might find. > I'm also decreasing the severity to minor but I don't feel too strongly > about this.
No problem - I understand how these things go. When a program finds a lock around from a previous incarnation, it's nice if it can do one of two things: 1. Tell you exactly where the lock file is, so you can delete it (Mozillas are really bad for hiding the lock file well) 2. Offer to force-delete the lock (Emacs does this well with "someone else is editing this file). Obviously, there are locks where you shouldn't do this, but when the item protected by the lock can be re-built trivially, it would seem a useful fix. cheers, Rich. -- rich walker | Shadow Robot Company | [EMAIL PROTECTED] technical director 251 Liverpool Road | need a Hand? London N1 1LX | +UK 20 7700 2487 www.shadowrobot.com/hand/overview.shtml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
