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

[feature request] recognize text editor URL schemes in links #2237

Closed
pmoura opened this issue Dec 4, 2024 · 3 comments · Fixed by #2238
Closed

[feature request] recognize text editor URL schemes in links #2237

pmoura opened this issue Dec 4, 2024 · 3 comments · Fixed by #2238

Comments

@pmoura
Copy link

pmoura commented Dec 4, 2024

I provide a Logtalk "diagrams" tool that supports creating diagrams for applications with links that open source code locations in common text editors and IDEs. The links use the text editors and IDE URL schemes. For example:

link: vscode://file//Users/pmoura/logtalk/examples/searching/hill_climbing1.lgt:35:0

But d2 (tested with version 0.6.8) doesn't recognize these URLs as valid and thus doesn't generate diagrams with links for nodes that contain them.

Common URL scheme prefixes include:

  • VSCode: vscode://file/
  • VSCodium: vscodium://file/
  • Cursor: cursor://file/
  • PearAI: pearai://file/
  • Windsurf: windsurf://file/
  • Zed: zed://file/
  • BBEdit: x-bbedit://open?url=file://
  • MacVim: mvim://open?url=file://
  • TextMate: txmt://open?url=file://
  • IDEA: idea://open?file=
  • PyCharm: pycharm://open?file=
@cyborg-ts cyborg-ts added this to D2 Dec 4, 2024
@jacobfriedman
Copy link

Watching this, ty- please add

@alixander
Copy link
Collaborator

Thank you, will be in the next release in ~a week

@github-project-automation github-project-automation bot moved this to Done in D2 Dec 6, 2024
@pmoura
Copy link
Author

pmoura commented Dec 6, 2024

Thanks!

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

Successfully merging a pull request may close this issue.

3 participants