Christoph> [1] I'll do that if I know the status of my other Christoph> "real" patches. Patches against 21.4 unless explicitly vetoed or returned for specific revision (usually by me) or approved (which usually happens just before a release, and so are normally announced by inclusion in the release announcement), are "pending because not understood." They generally stay that way for quite a while, because 21.4 is feature frozen. They are basically the lowest thing on my priority list, except for my personal development projects. The fastest route to inclusion in a stable XEmacs for such patches is submission for inclusion in the devel codebase or the Windows branch of 21.4, testing, and then recommendation for 21.4. The fastest route to getting your work to the users (who admittedly need it) is to create a Lisp package which redefines those functions appropriately. This will also get the feedback necessary to convince me that the code is safe enough for the core. For some reason this path is attractive to nobody, though. I really don't understand why everybody insists on surgery first when various forms of rehabilitative treatment would decrease risk for the patient, and hasten recovery. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Don't ask how you can "do" free software business; ask what your business can "do for" free software.