Re: [VETO] Re: XEmacs-21.4.5 info-look; sync with Emacs-21.1

SJT> That is negligible compared to the waste in time for the 3rd SJT> party developers who want to support both GNU Emacsen. SY> I would hardly call it a waste in time. Core GNU Emacs people certainly would, and people who are closer to the GNU project than to XEmacs probably would. But many of our packages come from just those people. SY> If we won't use our stuff, why should anyone else? [1] We do, in core, and in packages where the "upstream" maintainer is an XEmacs person. SY> The next step after that is packages. The packages are not "us", they're mostly third-party. In many cases originally developed and still maintained by GNU Emacs people for GNU Emacs. SY> Has anyone bothered to ask Kyle about it? Kyle, are you still SY> reading xemacs-beta? Why don't you use extents instead of VM does use extents on XEmacs. But the compatibility API uses the _name_ "overlay", and of course on GNU Emacs the VM functionality is implemented using overlays. Steve Baur, who intentionally wrote footnote.el as an exercise in GNU/XEmacs compatibility, uses a mixture of markers (to find things) and text-properties (for faces). Bletch, although it's barely acceptable in footnote. SY> overlays? Do you find extents lacking in some way? Do we SY> need to improve them somehow? There is breakage in extents, especially on Mule (changing the coding in a buffer destroys all the extents due to difficulties in figuring out character <-> byte mappings in such an inconsistent case). But that's not the issue. SY> [1] BTW, when was the last time anyone wrote an XEmacs module? SY> They sound like a nifty idea to me. I think we should be SY> encouraging development there too. Andrew Begel at UC Berkeley is doing very active development of "something" with modules, as is Jerry James ("something else") at U Kansas. -- 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.