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

Add more options #6

Closed
eight04 opened this issue Nov 29, 2016 · 3 comments
Closed

Add more options #6

eight04 opened this issue Nov 29, 2016 · 3 comments

Comments

@eight04
Copy link
Owner

eight04 commented Nov 29, 2016

Currently (~7.3.1), Linkify Plus Plus is so greedy that you can only stop it by adding specified elements to ignore filter. Should we let users adjust more detail behavior?

Current:

Strict mode? (not implement yet)

  • The link must be surrounded by spaces.
  • If it is not surrounded by spaces, it must be surround by separate characters (e.g. brackets) that surround by spaces.
  • Force lower-case domain.
  • Limit the length between each period in the domain.

References:
https://greasyfork.org/en/forum/discussion/comment/28440
http://markdown-it.github.io/linkify-it/

@eight04
Copy link
Owner Author

eight04 commented Dec 6, 2016

surrounded by spaces and fuzzyip options are added in 7.4.0.

@eight04 eight04 closed this as completed Dec 6, 2016
@tophf
Copy link

tophf commented Feb 19, 2020

The option works great but I still wonder why the underscores are considered as separators by default? Do people often type things like _www.site/foo_ ?

@eight04
Copy link
Owner Author

eight04 commented Feb 20, 2020

I don't remember. Probably some sites use it as a separator? (e.g. markdown?)

An interesting thing is that trailing underscores are not removed so _www.site/foo_ becomes _[www.site/foo_].

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

No branches or pull requests

2 participants