You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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)
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.
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.
The text was updated successfully, but these errors were encountered: