Bug 65346
Summary: | mouse-avoidance-fancy-hook needs guarding | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Reuben Thomas <rrt> |
Component: | xemacs | Assignee: | Jens Petersen <petersen> |
Status: | CLOSED RAWHIDE | QA Contact: | Aaron Brown <abrown> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 20030629-1 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-07-01 22:39:20 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Reuben Thomas
2002-05-22 14:56:00 UTC
*** Bug 65349 has been marked as a duplicate of this bug. *** Heard anything more from upstream? That's really where a fix should go in... for the problem, not the symptom I've reopened this one upstream, and so far had the response "your patch isn't really a fix, so we'll put it on the todo list." i.e. no ETA for a real fix. I'm trying to convince them that since it's a cosmetic problem, a cosmetic fix is acceptable, at least in the interim (since ATM it's simply broken). But no response to this yet. Do you know which function in `mouse-avoidance-fancy-hook' is causing the problem? Is it 'mouse-avoidance-too-close-p'? Perhaps you could try catching the error there instead to see if that is the case? Catching the error in mouse-avoidance-too-close-p seems also to fix the problem, though I suspect the real problem is that the value in mouse-avoidance-point-position can be out of date by the time it is used. I notice that it says in the code that the definition of mouse-avoidance-point-position is different in FSF Emacs. But as I said before, it's just a cosmetic problem that needs fixing, not a real bug... Well, I guess the definition of `mouse-avoidance-point-position' is different from in Emacs, because there is no `window-edges' function in XEmacs. It's not possible to get a backtrace of when `mouse-avoidance-fancy-hook' flakes out, is it? It would be nice to know exactly why its going wrong. I don't really see why the value from `mouse-avoidance-point-position' or `mouse-position' being out of date should cause any error, but I'm probably missing something. The bug occurs fairly rarely, but I've switched on Options->Troubleshooting->Stack trace on error. It's a little irritating, because it causes stack traces fairly regularly, but I'll try to stick it out until I get the fancy-hook error (I've tried to provoke it but without success so far). Adding a condition-case to next xemacs-sumo build. Should be fixed in xemacs-sumo-20030629-1. |