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

proposal: formal URI scheme for code locations #34654

Closed
l0k18 opened this issue Oct 2, 2019 · 3 comments
Closed

proposal: formal URI scheme for code locations #34654

l0k18 opened this issue Oct 2, 2019 · 3 comments

Comments

@l0k18
Copy link

l0k18 commented Oct 2, 2019

I wasn't sure where to leave this, but I have been working on a logging system that is more debug friendly (it inserts code location references instead of using arbitrary subsystem names) and I saw that VTE now has a feature to encode arbitrary text to be a URI https://gist.github.com/egmontkob/eb114294efbcd5adb1944c9f3cb5feda

All that is needed is a formal syntax for a Go module source location URI, I suppose that means a protocol identifier, and a thing that puts that protocol into a system mimetypes table and allows xdg open operations to assign a specific application to it. Then logs can use shorter links that take you to source code without specific configuration to recognise a source code path (sadly nobody makes an IDE with a terminal as good as a proper native one).

Not a very high priority proposal at all, but as I understand it, it is intended that go modules function as a unified decentralised filesystem namespace so a URL for this would simplify and enhance the UX for developers searching code and sharing locations and so forth.

Apologies if this is the wrong place to put this.

@gopherbot gopherbot added this to the Proposal milestone Oct 2, 2019
@bradfitz
Copy link
Contributor

bradfitz commented Oct 2, 2019

What are you proposing?

I see stuff about terminal escape sequences to link to things, and URLs, and logging, and go modules.

I'm lost.

@l0k18
Copy link
Author

l0k18 commented Oct 3, 2019

something that describes the path to a go repository so a relevant application can be used to view the document (eg go get and then open in your code editor)

@bradfitz
Copy link
Contributor

bradfitz commented Oct 3, 2019

This proposal is still too vague. You want a new URL scheme defined for ... Go code? What do you want encoded in it? Why don't you start with a strawman proposal so we can understand what you're looking for.

@l0k18 l0k18 closed this as completed Oct 12, 2019
@golang golang locked and limited conversation to collaborators Oct 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants