Re: Hideshow

Hrvoje> But imagine trying to port the extents API or the Hrvoje> specifier API under FSF. Agreed, those really can't be done in full. But there is a compatibility layer for extents available for GNU Emacs somewhere, that's about as good as overlay.el for those things where text properties are the wrong API. And Custom replicates most of what specifiers do, more or less, plus a couple of small tweaks that apparently specifiers can't do by themselves currently. Hrvoje> Not to mention things like toolbar APIs, glyphs, keymaps, Hrvoje> etc. The glyph issues reduce to specifier issues. In most cases where you just want an image for GUI and a text alternative for TTYs, there should be a way to kludge up a restricted API from GNU. AFAIK the keymap APIs are mostly the same, aren't they? It's just that GNU programmers often don't use the API, but if they did it should work, right? And if I can ever get out from under the spam flood, I've got a reasonable implementation of a toolbar API which provides the same set of convenience functions for XEmacs and GNU Emacs, and does something sane where the GNU Emacs API simply can't handle what XEmacs can (for example, because of all the cruft that GNU Emacs keymaps have accumulated, it makes no sense to try to insert a toolbar button at "third from the left", and IIRC there's no way to push a subset of buttons flush right in GNU; in those cases the implementation just willy-nilly inserts at the right-hand end of the toolbar). [The reason this hasn't been published already is that I puked my guts out when I realized that the GNU docs aren't free, not to us[1], and even months later haven't had the stomach to return to the project to remove the GNU manual quotes and rewrite documentation for the things that are kludged for the GNU side. And it really doesn't make much sense to publish it just for XEmacs.] Footnotes: [1] There is no small set of agents that own 100% of our copyright, not even the FSF, so we can't change it to FDL without rewriting everything that isn't provably 100% FSF-owned, or getting explicit permission from the authors. But we can't use FSF docs unless we change to FDL, or get the FSF's permission to use the docs under the existing XEmacs doc license (which is, of course, the old GNU Emacs doc license). -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.