GNOME Bugzilla – Bug 618399
Navigating to Go source files through links in External Tools output
Last modified: 2020-11-24 10:17:38 UTC
Created attachment 160851 [details] [review] patch for fixing this issue In gedit 2.28.0 (Ubuntu 9) the file paths and line numbers in Go's stack traces and the GoSpec testing framework's reports were clickable links. In gedit 2.30.2 (Ubuntu 10.04) it is not anymore possible to click them and navigate to the file. The attached patch adds support for those links. Related discussion: http://mail.gnome.org/archives/gedit-list/2010-May/msg00003.html (first post) http://mail.gnome.org/archives/gedit-list/2010-May/msg00024.html (comments about the patch)
Sorry for the late late response, today I was fixing some bugs in the link parsing and I think this should be working now. Could you please check?
Is somewhere a nightly build which I can try? I'm having a hard time compiling gedit myself. I tried running the unit tests which are attached to this issue, and they fail. Did you run them and get them pass?
yup, they work fine here. You will need to wait until next week to get the next tarball for gedit 3.2.1, in the mean time you can use jhbuild to get it built from git.
Esko, were you able to verify fix in gedit 3.2.1 or later ?
I tried gedit 3.2.1 (the binary which Ubuntu installed for me) and it did not work. The file paths were not clickable in External Tools' bottom pane. Here is the test data which I used: http://pastebin.com/pN92GC5E http://pastebin.com/QmRSEvF9 http://pastebin.com/EqS9eU1w
Reopening as per last comment.
Mass-closing of all gedit-plugins bugzilla tickets. Special "code" to find again all those gedit-plugins bugzilla tickets that were open before the mass-closing: 2bfe1b0590a78457e1f1a6a90fb975f5878cb60064ccfe1d7db76ca0da52f0f3 By searching the above sha256sum in bugzilla, the gedit contributors can find again the tickets. We may be interested to do so when we work on a specific area of the code, to at least know the known problems and possible enhancements. We do this mass-closing because bugzilla.gnome.org is being replaced by gitlab.gnome.org.