These two items in the changelog do not sufficiently explain what the changes are:
- Added a custom regex engine that matches multiple regexps in parallel, for faster file loading and indexing
- Improved Unicode support, including combining character rendering, character classification in regex searches, and case insensitivity in Goto Anything matching
Does the custom regex engine have any documentation?
It certainly has not improved Unicode support for me. I am now unable to use the hexadecimal escape \x and that’s destroyed most of my ability to work with Unicode.
- When I use \x, the search doesn’t find anything, and I get an error message (here I’m trying to find the letter “a” with its hexadecimal number 61).
Hexadecimal escape sequence was invalid. The error occurred while parsing the regular expression: ‘>>>HERE<<<\x{61}’. in regular expression \x{61}
.
2. I tried using \X, but the search now treats {61} as if it were the interval operator, and \X as if it were “any character.” The search highlights the text from my cursor to the 61st character after it:
Most of my job involves regular expression searches and non-Roman alphabets, and not being able to search for Unicode characters with hexadecimal escapes has made my job essentially impossible.