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

Not recognizing newer top-level domains #163

Closed
Berzerker opened this issue Aug 23, 2014 · 3 comments
Closed

Not recognizing newer top-level domains #163

Berzerker opened this issue Aug 23, 2014 · 3 comments

Comments

@Berzerker
Copy link

Example here: http://imgur.com/DJpf199

Seems like the newer top level domains are confusing putty a bit.
FauxFaux added a commit that referenced this issue Nov 9, 2014
@FauxFaux
GH-163: update "sensible" regex with new tlds
f61c710 
This is probably a losing battle.  Maybe I should just give in and recommend people use the "nearly any" option.

$ echo $(grep '^\.' tlds | cut -c2- | egrep -v '^[a-z]{2}$' | sort | uniq) | fold -w 61 -s | tr ' ' '|' | sed 's/^/"/;s/$/"/'
@FauxFaux
Copy link
Owner

FauxFaux commented Nov 9, 2014

I've added loads more things to the list.

This is probably a losing battle. Maybe I should just give in and recommend people use the "nearly any" option.

@FauxFaux FauxFaux closed this as completed Nov 9, 2014
@Berzerker
Copy link
Author

Ok, well, with the new update, a lot of non-standard TLDs, and even ones that were working before (like bit.ly) have stopped being recognized, changing to "nearly any" works.

@incognico
Copy link

@Berzerker you could use some more generic regex like (([a-zA-Z]+://|[wW][wW][wW]\.)[^ '")>]+)

@samcook samcook mentioned this issue Dec 19, 2014
Closed
@wilkowy wilkowy mentioned this issue Dec 20, 2014
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@FauxFaux @Berzerker @incognico