>>>> "Tak" == Tak Ota
<Takaaki.Ota(a)am.sony.com> writes:
Tak> Lastly, as I explained in the comment in table.el there is
Tak> one serious problem in table.el to be compatible with Xemacs.
Tak> It is how Xemacs implements intervals for Emacs notion of
Tak> text properties. When undoing some editing operation on text
Tak> properties things are reasonably reversible. However, under
Tak> current Xemacs interval implementation once joined interval
Tak> does not seem to separate correctly by undoing the last
Tak> operation that has joined the originally separated intervals.
Can you give an explicit example? I don't have a copy of table.el at
the moment. Specificially, what is "incorrect" about the separation?
Also, are you using the text property interface, the "overlay
compatibility" interface, or the native extent interface?
Tak> A section in the emacs lisp info explains this better than I
Tak> did above. Following is that page.
Typical FUD. In Japanese, "tatemae." Do not trust the GNU manuals'
explanations of "why XEmacs can't work". (I leave the
"hon'ne" to
your imagination.)
Specifically, they internally implement text properties as a table of
intervals, so we can emulate with extents (and if necessary extend the
core C code for efficiency). It turns out that in practice there are
satisfactory answers to _all_ of the problems posed in that node, as
long as you define "satisfactory = sensible defaults + flexible API".
Most likely the problem here is an unusual case that our current code
doesn't account for. If it's that unusual, we can change the behavior
without affecting other code, or if necessary we extend the API.
When you run into difficulties, feel free to ask us for help. Usually
together we can find a satisfactory implementation.
--
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.