Re: [AC] help synced with FSF and removale of button-2

Mats Lidell writes: Right. This is a complete API break, it needs to be described that way. It won't fix the breakage you cause, but at least they'll understand what happened (or feel sheepish when you tell them it's in the changelog). Also you can make it clear there's a new function that does pretty much the same thing. This is especially important when the change isn't one-to-one (I think you remove two functions and replace them with one general one?) A more complex strategy is to keep the old code and make sure nothing in core or packages uses it. Then use `make-obsolete' to inform users (although they may not compile their inits, in which case they won't see a warning from the compiler). No, you're doing the right thing. Either you keep the old code or reimplement it with pretty close to the same semantics using the new code, or you just break things, and hope there's not much of that. In this case, there probably is not -- I would say just do the sync, document it, and hope. Yeah, I'm just saying that if the test actually tries to call `help-mouse-find-source-or-track', it should fail loudly. _______________________________________________ XEmacs-Patches mailing list XEmacs-Patches(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-patches