/PuTTYTray

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

Comments

Assignees
No one assigned
Labels
None yet
Milestone
No milestone
3 participants
@Berzerker @FauxFaux @incognico
@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

@FauxFaux
GH-163: update "sensible" regex with new tlds 
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/$/"/'
f61c710
@FauxFaux

This comment has been minimized.

Show comment
Hide comment
@FauxFaux

FauxFaux Nov 9, 2014

Owner

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.
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 Nov 9, 2014

@Berzerker

This comment has been minimized.

Show comment
Hide comment
@Berzerker

Berzerker 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.

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

This comment has been minimized.

Show comment
Hide comment
@incognico

incognico Nov 22, 2014

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

incognico commented Nov 22, 2014

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

@samcook samcook referenced this issue Dec 19, 2014

Closed

Fix "sensible" url regex #181

@wilkowy wilkowy referenced this issue Dec 20, 2014

Closed

0.63-t022 has broken hyperlinks matching #182

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment