Re: next-single-char-property-change on xemacs vs emacs
On 2/11/11 8:09 AM, Stephen J. Turnbull wrote:
Raymond Toy writes:
> Is this difference intentional? FWIW, it breaks slime, which assumes
> Emacs' behavior. For right now, I'm just doing
>
> (or (next-single-char-property-change <args>) (point-max))
Is this behavior actually useful?
Yes. Slime basically does (goto-char (next-single-char-property-change
<args>)), which obviously breaks with xemacs when n-s-c-p-c returns
nil. The args don't include the object parameter, and thus defaults to
the current buffer. (point-max) should be the right thing, then, I
think. At least emacs says n-s-c-p-c is supposed to return the end of
the object when there is no more n-s-c-p-c.
Ray
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta