Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

@Berzerker Berzerker commented Aug 23, 2014

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
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 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 Nov 9, 2014
@Berzerker
Copy link
Author

@Berzerker Berzerker commented Nov 22, 2014

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

@incognico incognico commented Nov 22, 2014

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.