Closed OneOfOne closed 7 years ago
I'm also seeing this issue. @OneOfOne does your code class or outline view still work? Mine returns nothing; no errors, but no content either. I'm guessing it is related since if you can't parse the code to display outline view, you can't parse it to jump around to different symbols either.
I've moved to a different project, however I tried to investigate this and I came up empty, there were no errors or anything that I could find.
Note that downgrading to x20.1 fixes this including the Outline view.
Mine stopped working after I imported a library (https://github.com/mattbaird/elastigo), I don't know where's the conflict, I'm trying to find it. If "Jump to declaration" stopped working for you, try to delete the latest installed library and see if the feature starts working.
Why would code in my GOPATH have anything to do with it? In that case, temporarily setting GOPATH to a new value and creating a quick hello world would resolve the issue. That doesn't resolve the issue for me. Does that actually work for you?
@mzimmerman, LiteIDE creates an index of all the functions, and some entities may break it. After setting GOPATH to a new value you need to wait for a few minutes, because the index is rebuilding.
I haven't yet pin pointed the code in that library that breaks indexing in Liteide, but removing that library totally worked out for me.
Also I noticed that auto-complete works, but none of Jump to Declaration/Expression Information/Find Usages work.
Where can I find more information on how/where that index of all the functions is built? Liteide x22 has been sitting for ~20 minutes where the only thing in GOPATH is a helloworld main.go file and has yet to generate any outline. If I use x20, it generates the outline virtually immediately.
Code completion is unrelated as Liteide uses the external gocode program to implement that.
@xyproto Do you have this issue with versions greater than x20? I can't run anything greater than that or I lose my code outline (among many other related features mentioned here) which is one of the primary reasons to use an IDE.
Any debugging symbols or debug code I can add to try and figure this out?
update: If I have my GOPATH set jump to declaration doesn't work. If I remove my GOPATH from view -> Manage GOPATH then it works again (I can't build but it works) just like @buryat I have elastigo in my project.
@mzimmerman, haven't experienced this issue yet, no
Well now I'm just completely stumped. How do I debug this? As far as I can tell, liteide doesn't have any debug flags for building. Where in the liteide code is the outline generation?
Using a completely empty GOPATH does not fix it. That is setting it with an environment variable and using the "Manage GOPATH" option in LiteIDE. @jiminoc, if you use a clean GOPATH does that make everything function correctly?
Probably fixed in liteide x24, please test again and report !
=[ not for me. Anything I can do to debug this? When I noticed it, I lost the Outline function; still is the case.
On Fri, Oct 24, 2014 at 4:52 PM, Vincent Vanackere <notifications@github.com
wrote:
Probably fixed in liteide x24, please test again and report !
— Reply to this email directly or view it on GitHub https://github.com/visualfc/liteide/issues/178#issuecomment-60447482.
In 25.0, everything seems to be fixed! :thumbsup: :running:
I tried LiteIDE maybe 9 months ago. Lack of multi-pane support was something of a showstopper for me (I grew so accustomed to this with Intellij that I can’t live without it).
I tried running multiple instances of LiteIDE as a work around but then got annoying popups “such and so file has changed, do you want to reload it” from instance A when saving instance B.
I’m presently using Sublime with GoSublime extension. It does great multi-pane but has other problems. Any plans for multi-pane in LiteIDE?
The second big disappointment for me was an inability to get even basic, visual debugging going using GDB, despite installing latest-and-greatest of everything and trying every suggestion I could find via google search.
Thanks for listening. —bill
On Dec 4, 2014, at 12:11 PM, Matthew Zimmerman notifications@github.com wrote:
In 25.0, everything seems to be fixed!
— Reply to this email directly or view it on GitHub https://github.com/visualfc/liteide/issues/178#issuecomment-65695087.
GDB support is broken / not supported in Go 1.3+ in general, has nothing to do with LiteIDE.
Neither right clicking a symbol and selecting any of these options nor using the keyboard shortcuts do anything, no errors, no warnings, nothing.
The same applies to go version 1.2 as well, is there anything I can help to debug this?