These are chat archives for ensime/ensime-atom

30th
Nov 2015
Matthew de Detrich
@mdedetrich
Nov 30 2015 09:53
@hedefalk Where is the .ensime_cache folder located
Arnout Engelen
@raboof
Nov 30 2015 10:01
@mdedetrich usually in your project root
Matthew de Detrich
@mdedetrich
Nov 30 2015 10:02
Cheers
Matthew de Detrich
@mdedetrich
Nov 30 2015 10:11
@raboof and @hedefalk Fixed my issue, it seems my the .ensime_cache folder had invalid entries to a package which didn’t exist. I just deleted it and its all working now
So yeah, ensime is starting, but I am still getting a lot of false error messages (mainly ensime saying packages in import statements don’t exist, when they do)
Arnout Engelen
@raboof
Nov 30 2015 10:19
cool! did you get any error message? perhaps we should add this as a suggestion to it?
Matthew de Detrich
@mdedetrich
Nov 30 2015 10:19
There were actually invalid tests, which didn’t compile, but I think imports (which didn’t exist in tests) where being carried over to the main project
Hmm nope, still happening. Basically in the line gutter, ensime is reporting that my imports don’t exist, when they do
And now I am getting presentation compiler crashes
Matthew de Detrich
@mdedetrich
Nov 30 2015 10:25
This is a fairly complex project, and its using stuff like shapeless/scalaz
Arnout Engelen
@raboof
Nov 30 2015 10:25
hmm not sure I'm not that deep into ensime itself yet...
Viktor Hedefalk
@hedefalk
Nov 30 2015 11:21
@mdedetrich Yeah, these are upstream ensime-server -> scala presentation compiler. Basically: ensime/ensime-server#673 There's not much we can do in ensime-atom about this I'm afraid.
Matthew de Detrich
@mdedetrich
Nov 30 2015 11:23
Jesus thats been around for ages
are there any known tickets for this issue?
Like on Scala itself, not on ensime
Viktor Hedefalk
@hedefalk
Nov 30 2015 11:32

Dunno status anymore. I used to report a lot of issues on the presentation compiler when I used scala-ide. Like:

https://scala-ide-portfolio.assembla.com/spaces/scala-ide/tickets/1000602-the-scala-compiler-crashed%E2%80%A6/details

There was something else before assembla too, don't remember. But I guess they're using github now?

In Eclipse I had to make a full clean rebuild when presentation compiler crashed which basically took forever and it happened all the time. Now I can at least continue typing :)

I would suggest reporting to presentation compile project with stack trace when you hit those issues. You should be able to find it in server log, just tail [project]/.ensime_cache/server.log. I'm going to start to do that.

Matthew de Detrich
@mdedetrich
Nov 30 2015 11:32
Well this is a company project, so I can’t really upload anything sensitive
Viktor Hedefalk
@hedefalk
Nov 30 2015 11:33
I see.
Matthew de Detrich
@mdedetrich
Nov 30 2015 11:33
So thats going to make it a bit hard :p
Viktor Hedefalk
@hedefalk
Nov 30 2015 11:36
Yeah, sorry. I can't do much but suggest modularizing so you don't really have a complex project anymore :) Try to boil those issues down to smallest possible and maybe you can share. Anyway, just the stack trace (which probably doesn't even mention your code until top frame) could maybe be enough for the scalac guys to find the problem? Maybe.
Matthew de Detrich
@mdedetrich
Nov 30 2015 11:36
We already did that, project is 26 modules. Ill see what I can do
Matthew de Detrich
@mdedetrich
Nov 30 2015 11:43
@hedefalk I guess this is the advantage of someone like IntelliJ using their own system for code completion, they don’t have to deal with these problems
Rory Graves
@rorygraves
Nov 30 2015 11:45
@mdedetrich The downside being often their own system gets it horribly wrong and horribly confused
Matthew de Detrich
@mdedetrich
Nov 30 2015 11:46
Yup, but their latest release is significantly better. It now works correctly 100% of the time, only exception is stuff like shapeless
Its also faster/uses less memory than before, although not as snappy as ensime
Arnout Engelen
@raboof
Nov 30 2015 11:47
@mdedetrich I feel your pain btw - I'm seeing all kinds of errors I don't see in sbt, but can't easily share the code as it's proprietary. Keep planning to boil it down to a small sharable project but can't really justify doing that in company time
Rory Graves
@rorygraves
Nov 30 2015 11:47
Yeah, IntelliJ is pretty neat. The bonus with ensime is that it doesn't block the editor - which is often why it feels snapier
Arnout Engelen
@raboof
Nov 30 2015 11:47
Makes me want to switch to writing OSS fulltime :)
Matthew de Detrich
@mdedetrich
Nov 30 2015 11:48
Yeah thats a big bonus, but if you haven’t, I would check out Intellij 15, at least if you want to check out the competition :p
Rory Graves
@rorygraves
Nov 30 2015 11:48
Me too, now if I could persuade someone to pay me for it....
I have checked it out - it is very neat
I hope Ensime can slowly catch up
Matthew de Detrich
@mdedetrich
Nov 30 2015 11:49
well you have a 30 day trial if you want to check it out quickly, there is also CE which may be good enoughfor checking out reasons
Rory Graves
@rorygraves
Nov 30 2015 11:51
I have a fair amount of experience with IntelliJ - CE is fine, because most of the paid for stuff is java centric.
Matthew de Detrich
@mdedetrich
Nov 30 2015 11:51
I mean as far as IDE’s go, its a really good one, in my opinion a lot better than Eclipse
Arnout Engelen
@raboof
Nov 30 2015 11:55
yeah IntelliJ is good, its git integration is nice too
Rory Graves
@rorygraves
Nov 30 2015 11:55
Yep, I concur
Arnout Engelen
@raboof
Nov 30 2015 11:57
it's the huge blocking waits that drive me to trying things like atom - and actually that might not even be their fault (could be some plugin or other holding up the system)
Rory Graves
@rorygraves
Nov 30 2015 11:58
I think thats part of my point, the Ensime seperation hides a lot of 'the presentation compiler has gone into a tailspin' from completely borking the editor part.
Arnout Engelen
@raboof
Nov 30 2015 11:59
exactly
Rory Graves
@rorygraves
Nov 30 2015 11:59
It obviously would be nice if the scala compiler threw less hissy fits ;)
Matthew de Detrich
@mdedetrich
Nov 30 2015 12:04
I don’t think IntelliJ has the infrustructure for async UI feedback, hence why it always blocks
normally this wasn’t an issue for stuff like Java, whos compiler is lightning fast
and also has a fairly straight forward type system
Hopefully Dotty will fix a lot in this area though
Rory Graves
@rorygraves
Nov 30 2015 12:07
We can hope
I'm actually trying to refactor some of the Ensime internals so we can support dotty
Currently we have too many dependencies on internal scalac stuff.
Matthew de Detrich
@mdedetrich
Nov 30 2015 12:09
Dotty is looking really good, I like the direction in which its gong