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

Only HTTP(S):// URLs are clickable #255

Open
RobertNotRob opened this issue Jul 16, 2024 · 3 comments
Open

Only HTTP(S):// URLs are clickable #255

RobertNotRob opened this issue Jul 16, 2024 · 3 comments

Comments

@RobertNotRob
Copy link

Describe the bug
Many applications support deep linking through implementing custom URI schemes. For example standard ones "file://", "ftp://" "mailto://" (defined here or custom ones such as slack:// vscode:// and binaryninja://. Only http(s):// URLs are rendered as a clickable link in the Heynote which I would consider a bug.
I commonly use these types of links in my workflow which makes the program difficult to use effectively.

To Reproduce
Steps to reproduce the behavior:

  1. Open Heynote
  2. Copy a deep link for any program (i.e
  3. Link is not rendered and is not clickable

Expected behavior
The link is rendered and can be cmd+clicked by the user.

Screenshots
If applicable, add screenshots to help explain your problem.
image

Desktop (please complete the following information):

  • OS: MacOS 14.4.1
  • Version 1.8.0
@heyman heyman changed the title Bug: Only HTTP(S):// URLs are clickable Make URLs other than HTTP(s) clickable Jul 17, 2024
@heyman heyman added enhancement New feature or enhancement and removed enhancement New feature or enhancement labels Jul 17, 2024
@heyman heyman changed the title Make URLs other than HTTP(s) clickable Only HTTP(S):// URLs are clickable Jul 17, 2024
@heyman
Copy link
Owner

heyman commented Jul 17, 2024

Not sure that I would consider this a bug. HTTP(S) links should be so much more common than any of the other protocols. VSCode seems to support file://URLs, but not any of the other protocols in the standard.

What's your typical use-case for this?

@RobertNotRob
Copy link
Author

RobertNotRob commented Jul 18, 2024

I would consider it a bug as it's not conformant to the RFC - but agree that it's subjective and HTTPS should cover a lot of usecases.

I'm using HeyNote as a floating scratch pad for keeping track of my train of thought. I'm trying to take notes while minimising the context switching - and an app like this is perfect for holding that.

Usually I'm doing some form of reverse engineering where I'm trying to figure out how a program works. I have a plugin for the tool I use to do this that enables me to extract segments of code - with a deeplink back to where I found it.

This is super useful as it enables me to get back to useful information in one click - but currently is broken as the "disas://" URLs are not clickable.

@RobertNotRob
Copy link
Author

On VSCode - the list for the editor is hard coded. There is a "Allow Link Schemes" setting for the terminal but no such setting for the editor, so instead you need to use a plugin dendronhq/dendron#1317

Another example of this kind of use would be to link to repositories like so: vscode://vscode.git/clone?url=https://github.com/heyman/heynote.git

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