Not a testing version, 2.09 – macOS non-pro version
didn’t know where else to report this.
What were you doing: typing ‘Plant.ID’
What feature did you use: keyboard input
What happened: A link was immediately created and text turned ‘blue’. Clicking on that link accessed the website that is Plant.ID. Further testing proved that any word with ‘.id’ or ‘.ID’ as suffix creates a link.
if there is a website with that URL the click opens it in default web browser.
What did you expect to happen: text displaying what i typed
Bear automatically makes text that looks like links clickable as you describe. The problem is that it is not easy to know for certain what is intended to be a link or not. In your case, what you wrote is a valid URL and it is even a web site.
Having links clickable is a nice feature, but having things that are not intended to be a link highlighted is an annoyance. I will think about it to see if we can improve on this.
Thanks for the feedback!
Also, one thing you can do is to add a backslash before the dot to escape it (
This is also an issue for many sort of paragraph references. For instance, try entering text like the following and it will unfortunately get converted into a hyperlink in Bear - a hyperlink that of course leads nowhere.
What’s really weird is that if you change the VI to V, then no hyperlink.
Additionally, references like the following are also converted into useless hyperlinks:
Same as above that if you change
in to some other text like
ix then no hyperlink.
So Bear has some weird logic about what it thinks should be a hyperlink and what should not be one.
It would be nice if ‘auto-hyperlinking’ were limited to standard TLDs.
Good feedback! It is helpful with more examples of things that aren’t links that are highlighted.
The logic isn’t as weird as you think. Bear has a list of all top level domains that it checks against.
.vi is a top level domain but
In the above example, we could use the fact that the string doesn’t end with the top level domain to exclude it from the link pattern. Perhaps we could also have a requirement to only use lowercase letters for the less common top level domains.
I think checking if the text ends with a lowercase TLD would be a great filter. Thank you!
I have made URL parsing a bit more restrictive to solve the above cases. Will be part of the next release.