On 2/9/11 1:28 PM, Helmut Eller wrote:
* Raymond Toy [2011-02-09 03:57] writes:
There's an issue with slime-search-property and xemacs. In xemacs, next-single-char-property-change returns nil if the property is not found instead of the end of the object as in emacs. This problem shows up when you're using M-p/M-n to find the next compiler note/warning in the source code. We get an error about (goto-char nil) when the last note is found.
I can't reproduce this in Xemacs 21.4 (patch 22). I see some oddness not reliably and never (goto-char nil). Do you have an example?
Found the reason. XEmacs 21.4 doesn't have next-single-char-property-change, so slime defines it's own version. XEmacs 21.5 has this, so slime uses the XEmacs version. I will have to ask the xemacs guys if this is a bug in 21.5. Ray