These are chat archives for ensime/ensime-atom

12th
Feb 2016
Viktor Hedefalk
@hedefalk
Feb 12 2016 06:38
@caente oh, that sucks. I have no idea. Which version are you at? I'm running both 1.5.1 and 1.6.0-beta1.
Ghost
@ghost~540393fe163965c9bc2018ce
Feb 12 2016 07:41
@hedefalk that's because you're a member of that group. If you do all here, it stays here
Miguel Iglesias
@caente
Feb 12 2016 13:58
@hedefalk version 1.5.2
same thing with 1.6-beta o_O oh well, I’ll keep looking
Miguel Iglesias
@caente
Feb 12 2016 15:19
ah weird, it works after sbt clean o_O perhaps what changed wasn’t in atom, but in our project...
Viktor Hedefalk
@hedefalk
Feb 12 2016 15:56
But this wasn't related to Ensime was it? I got it that Atom itself hanged just by opening the project? Or was it when starting Ensime?
Miguel Iglesias
@caente
Feb 12 2016 16:58
I don’t think it was related to ensime, I posted it here because… I’m already in this channel
scratch that I know for a fact that it had nothing to do with ensime
it was disabled at the time
Viktor Hedefalk
@hedefalk
Feb 12 2016 17:01
@caente Ok, cool. But then it seems really weird that an sbt clean would make any difference for Atom?
Miguel Iglesias
@caente
Feb 12 2016 17:03
I suspect there was some weird lengthly files in generated from a ctags command
and atom died trying to index them
since I have the ctags package installed
(the tags file were in /target )
Viktor Hedefalk
@hedefalk
Feb 12 2016 21:42
Ah.
Alexey Alekhin
@laughedelic
Feb 12 2016 21:45
@hedefalk thanks for fixes. I finally got those messages ") it's much better to know that something didn't work than a silence... ☺️
Viktor Hedefalk
@hedefalk
Feb 12 2016 21:48
I've noticed that a stop server, rm -r .ensime_cache, start server cycle sometimes makes the indexer find the source location that it didn't before.
@laughedelic .
Alexey Alekhin
@laughedelic
Feb 12 2016 21:52
thanks! I'll try it next time I encounter problems