github-actions[bot]
commented
10 months ago Thank you very much for opening up this issue! I am currently a bit overwhelmed by the many requests that arrive each week, so please forgive me, if I fail to respond personally. I am still very likely to at least skim read your request and I'll probably try to fix all (real) bugs if possible and I will likely review every single PR being made (please, give me a heads up if you intent to do so) and I will try to work on popular requests (please upvote via thumbs up on the original issue) whenever possible, but trying to respond to every single issue over the last years has been kind of draining and I need to adjust my approach for this project to remain fun for me and to make any progress with actually coding new stuff. Thanks for your understanding!
ishanarora
Jagdfalke
Problem Statement
Many desktop and mobile apps support their unique dedicated protocol prefixes for creating app specific URIs, e.g. for a specific note in a note taking app, or for a specific email thread in an email client.
When URIs are present in task description / notes, they appear clickable in the markdown rendering for only a small selection of web protocols, while all other URIs are not clickable.
:grey_question: Possible Solution
Make all URI patterns clickable. Additionally, perhaps add a right-click context menu with options to open the URI link, and copying the URI. ## :arrow_heading_up: Describe alternatives you've consideredEnter the inline markdown editor, and select the URI text, copy it, and open the URI through a third-party program. It works but it's inefficient, and prone to error when selecting the URI text i.e. not super-productive :smiling_face_with_tear:
:heavy_plus_sign: Additional context
NA