These are chat archives for ensime/ensime-atom

8th
Mar 2016
Viktor Hedefalk
@hedefalk
Mar 08 2016 08:01
Hm, @d6y you added a trailing new line thing for the docs port, right? Did you have the same problem as @trepidacious with that? I could just add the same thing for the api port?
Rory Graves
@rorygraves
Mar 08 2016 08:03
I think this should a server fix.
Viktor Hedefalk
@hedefalk
Mar 08 2016 08:04
I never had a problem myself though…
Viktor Hedefalk
@hedefalk
Mar 08 2016 08:15
@trepidacious I have published a patched ensime-client node package that adresses the trailing newline. If you edit package.json in ~/.atom/packages/Ensime to use ensime-client 0.2.3 and then run npm install it should work.
Rory Graves
@rorygraves
Mar 08 2016 08:32
I thought that error showed it was an error when the server read the file?
Viktor Hedefalk
@hedefalk
Mar 08 2016 08:33
Oh, ok.
Yeah, you're right!
Ah, it's the new server feature of reading the port file, before it just wrote it…
Ok! The ball is YOURS @rorygraves !
Rory Graves
@rorygraves
Mar 08 2016 08:35
Lol. I'll put a fix in this morning.
Rory Graves
@rorygraves
Mar 08 2016 09:39
ensime/ensime-server#1339
trepidacious
@trepidacious
Mar 08 2016 11:12
I've built an assembly.jar, how would I get atom to use it to try it out?
trepidacious
@trepidacious
Mar 08 2016 11:49
Thanks, working now :)
trepidacious
@trepidacious
Mar 08 2016 21:47
This may not be the best approach, but could there be a setting to disable red squigglies? Maybe it's just my project, but I get ~100 false errors on valid projects and it's distracting. Autocomplete and go to definition etc. still seem to work fine so ensime's still definitely useful.