bug#33205: 26.1; unibyte/multibyte missing in rx.el

[Mattias Engdegård]

I tried using rx to match raw bytes. (rx (any (?\200 . ?\377))) doesn't work, 
since that is translated to the corresponding Unicode range; (any (#x3fff80 . 
#x3fffff)) must be used instead. Maybe that is evident, or would it merit a 
mention in the doc string?

The alternative formulation (rx (any "\200-\377")) doesn't work either, and 
this seems to be a bug. Looking at rx-check-any-string, a second bug is 
revealed: the code uses the regex ".-." to pick out ranges, which means that \n 
cannot be a range endpoint.

Perhaps you want me to open a new bug for the above? I'm attaching a patch all 
the same, but you may prefer doing it differently.

rx-any-raw-bytes.patch
Description: Binary data