These are chat archives for ensime/ensime-atom

25th
Jan 2016
Andrew Gaydenko
@gaydenko
Jan 25 2016 15:07
Hi! Must ensime:stop stop ensime server? Or what does it do? :smile:
Andrew Gaydenko
@gaydenko
Jan 25 2016 15:14
And another question. I have got false positive errors against implisits: say, all 1.hour and other durations say about not-having hour method for Int, or map literal notation "a" -> 1 says about not-having -> method for String. Is it expected behavior at the current ensime-atom state? (the project in hands is correct, of course, and .ensime is the same one working with ensime-emacs without errors or even warnings; ensime cache was regenerated).
Viktor Hedefalk
@hedefalk
Jan 25 2016 15:26
ensime:stop stops the client and "maybe" the server depending on settings. At least that's the idea :)
Weird with the false positives. Shouldn't be client dependent since it is always upstream issues with presentation compiler…
Andrew Gaydenko
@gaydenko
Jan 25 2016 15:29
@hedefalk , then @fommil hides some errors from me with ensime-emacs :smile: as far as .ensime is the same.
Viktor Hedefalk
@hedefalk
Jan 25 2016 15:58
Hm…
Andrew Gaydenko
@gaydenko
Jan 25 2016 16:27
@hedefalk , I'm very new with atom - just the first touch. So I didn't recognized the shortest way to reproduce the false positive. But some signs are:
  • just after session start all is OK (and, say, autocompletion and Ctrl-clicking do work)
  • to provoke the issue I must edit a code this or that (which?) way
  • typecheck all also results in the issue (dozens of false errors for mid size project)
And, well, I must add, I have dedicated terminal running sbt session with ~stage - which includes ~compile - being active.
Viktor Hedefalk
@hedefalk
Jan 25 2016 22:05
Sorry all Windows users. Apparently 0.32.0 is borked for Windows users that are not already node script kids. Build path dependencies like Python and such. I'm looking into if it possible to easily fix: https://github.com/atom/scandal/issues/34#issuecomment-174678503 In the meantime you just have to stick with 0.31.1.