So if I am manually using \OM or \OL in a Brief regex, I need to do them in upper case too? If so, that would explain why \OM has not worked on occasion when I have been trying to use it.
Modifying tbregex.e brings up a problem that I have been running across recently. I also have a modified seldisp.e, where hs2 was kind enough to provide me with a fix for the selective display GUI not using my default of Brief regular expressions. I have been keeping the modified seldisp.e in my "custom" directory alongside my own macros, so that it will not be overwritten by a hotfix or an update installation. Each time I do a hotfix, I have to manually check if there was a change made in seldisp.e, and if so, merge it, and then reload my modified seldisp.e. I hope eventually that the fixes will be done in the original too, in this case (and now for tbregex.e), but I am sure at some point I will be making changes that will be personal to me and will never be becoming part of the released version. So I would like to propose that there be a mechanism to handle this situation when hotfixes and updates are applied. There are probably a number of ways of doing it, but the one that sprang to mind was to have the update process check the first line of each of the macro files it is updating, to see if there is a comment saying:
/*:: Customised */
or for those of us who speak American English:
/*:: Customized. */
If so, it would create a backup copy of the .e file as .e.custom before it updated to the new version of the file. At the end of the hotfix or update process it would pop up a list of all such files it found, preferably in a format that could then be directly used to diff all the files on the list and do merging. It would be nice if it also created a .e.release file as a copy of the newly installed updated .e file, so that the release version was always available for comparison without my having to copy it manually.
