Michael Toomim <toomim(a)OCF.Berkeley.EDU> writes:
The more recent stable versions of xemacs don't seem to mention
any fixes
of this nature. Can anyone verify this on a new release? Is this a true
xemacs bug (or a documentation bug?)?
It happens in the recent betas as well. I think the current behavior
is a bug because there is no way let the extent behave the way you
want otherwise.
Jan