>>>> "sjt" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
sjt> Why? Basically in your explanation of how the soe works, you
sjt> are saying that large extents (not just extents covering the
sjt> whole buffer, but any extent that overlaps many other
sjt> extents) are very expensive because they make _all_ the
sjt> overlapped extents inefficient. So that means that code like
(let ((header (make-extent (message-beginning) (header-end)))
(body (make-extent (header-end) (message-end))))
(font-lock-fontify-buffer))
sjt> necessarily sucks. If I'm not totally missing the point, I
sjt> have to ask: Do you consider that restriction acceptable?
For example, here's the output of (extents-at (point)) in a Gnus
summary buffer:
(#<extent (1, 10542) D paste-function text-prop 0xa062cec> ;; Uh-oh....
#<extent (10425, 10465) D paste-function gnus-number text-prop 0x9f51b64>
#<extent (10425, 10464) D paste-function text-prop 0xa068620>
#<extent (10432, 10463) HD paste-function text-prop 0x9f51d24>
#<extent [10432, 10463) 0x9f7b32c>)
Apparently there are 4 such extents per line, and one line per
article. And
One extent to rule them all, and in the slowness bind them.
--
School of Systems and Information Engineering
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.