The regular expression used by UltraEdit/UEStudio for finding strings which can be interpreted as a URL is built-in and is not customizable.
I suggested initially during beta testing of UE/UES 2023 a Perl regular expression to detect only strings as URLs beginning with
http:// or
https:// or
ftp:// and other protocol identifiers followed by a sequence of characters according to the
URL specification. It looks like the regular expression was modified in several versions later because of requests by users. The file
changes.txt in program files directory as well as the information published for hotfixes lead me to this assumption. There is now interpreted as a URL every string with letters, digits and other ASCII characters valid in a URL followed by a dot and more letters, digits and other ASCII characters valid in a URL (and that sequence optionally multiple times like for an IPv4 address) and a slash character even on no protocol identifier is present at the beginning of this string. An IPv4 address itself is not identified as a URL, but an IPv4 address followed by a slash and the number of ones in subnet mask is false positive identified as a url as that sequence of characters is the same as
www.ultraedit.com/ from a regular expression point of view.
A string like
10.10.110.12/23 in a file which contains IPv4 addresses without or with number of ones in subnet mask is interpreted by a user with knowledge about that syntax not as URL in this context but is at the same time a valid URL according to the URL specification. The context makes the difference which UE/UES does not know. It would be possible with C++ code to validate if the found URL string is a valid IPv4 address (0–255
.0–255
.0–255
.0–255) followed by a slash followed by number of ones of subnet mask (1–31) and exclude in this case the found string from URL underlining and URL highlighting. But there could be also use cases where such a string is indeed a URL of a device referenced with its IPv4 address and file in root directory of which name consists only of one or two digits. Such a URL is unusual but possible.
It is up to you sending an enhancement request by email to support of UltraEdit for an enhancement to filter out valid IPv4 addresses followed by a slash followed by a number in range 1 bis 31 and no more characters before and after such a string from URL underlining/highlighting or making the regular expression used for URL detection customizable by the user (if there is still used only one and not already multiple regular expressions which I do not know).
It is of course also possible to just uncheck the configuration setting
Underline URLs and do not use the feature which would improve also speed as in this case UE/UES does not need to search all the time in currently displayed text which strings could be URLs and underline them which must be updated also on every edit like on typing a URL or editing a URL. A user can nevertheless always open a real URL in a text file by right clicking anywhere in the URL string and left clicking in context menu on first menu item for opening the URL in the default browser. The same can be done also with a hotkey assigned to the command
Open file/URL under cursor in the
Key mapping configuration which is the method used by me. I do not need underlining or syntax highlighting URLs, I can see myself which string is a file name or a URL in the current context of active file content.
By the way: The feature for opening a file or URL under cursor uses obviously as different expression or algorithm to identify a URL because of
10.10.110.12/23 is not identified as URL while
www.ultraedit.com even without a slash at the end is identified as URL in comparison to the underline URLs feature. I detected that difference just now which is unexpected by me.
You can send also an enhancement request to get underlined IPv4 addresses which do not have appended a slash and the number of ones in subnet mask. But that should be really an extra configuration because I am quite sure that many other users do not want strings being just an IPv4 address in their text files underlined together with real URLs. The context makes again the difference.
