I've verified this in XEmacs 21.4.13 (RHEL 5).
The scenario runs something like this:
Do a successful string match in a read-only buffer, ie. the
match string data gets set.
Switch to a writable buffer, do an unsuccessful string match
followed by a replace-match.
I see the text in the read-only buffer get changed. This is a
no-no unless inhibit-read-only is set and it isn't.
I'll post a test case and check 21.5 after work, unless this has
come up before and you've already fixed it.
Ugh. We've also got an interface divergence of the ugliest sort
with FSF 21.3.
-sb
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta