Skip to content
This repository has been archived by the owner on Apr 19, 2024. It is now read-only.

.im TLD not recognised #177

Closed
wodim opened this issue Nov 20, 2014 · 4 comments
Closed

.im TLD not recognised #177

wodim opened this issue Nov 20, 2014 · 4 comments

Comments

@wodim
Copy link

wodim commented Nov 20, 2014

The .im TLD is not recognised in URLs.

@wodim
Copy link
Author

wodim commented Nov 24, 2014

Well, after several days of use, I must say that most URLs are not recognised at all.

@stfnm
Copy link
Contributor

stfnm commented Nov 25, 2014

I personally prefer the setting Window -> Hyperlinks -> URL selection -> Select nearly any URL, which does pretty much what its name already suggests; select nearly any URL (including .im TLDs).

@u1735067
Copy link
Contributor

"([a-zA-Z0-9\\-]+\\.)*[a-zA-Z0-9\\-]+\\." // ab-c.de-f.qrs.tuv.

This is not good, it is forcing the tld to be in the following list. But why this huge useless regex ? If the text already starts with (https?|ftp):// or www, why trying to validate the tld (non-fixed list) ?
With this regex my link https://trac.mysite.fr/ticket/150 if only matched as https://trac

If someone is looking for the liberal regex, it is here :

const char* urlhack_liberal_regex =

@VilleSalonen
Copy link

Could "Select nearly any URL" be used as a defalt value? Are there any problems with that for majority of the users?

FauxFaux added a commit that referenced this issue Apr 11, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants