@hedefalk Been busy last week but I tried the new Atom plugin and cleaned out all caches again and now ensime runs for akka-persistence-cassandra. Thanks for trying it out earlier so I knew it wasn’t something in the project!

I’m confused about these javascript overlays, it just seems very fragmented to me. In a project they had started using Coffee Script a while back but it just caused confusion when fixing bugs since javascript is a dynamic language. We went back to javascript.

Well, I'd say it's a matter of setup pain to fix stuff like building and sourcemaps, but today you can very much have zero penalty polyglotism in a node environment.

I personally can't stand writing/reading javascript as little as I want to code in Java.

Coffeescript can definitely lure you into feeling safe when you shouldn't, but I still think it's a hell lot better than Javascript. But I think I'm gonna rewrite the ensime-node-client lib now in Typescript so I can use it better from ensime-vscode. It's always good to learn new languages too.

@hedefalk well maybe my memory have muddled things. We had backbone as well and how the systen was implemented with that contributed considerably. Still, not having the same source in your editor as in your browser when you get an exception on line 1005 causes a mental stumbling block. But with source maps things might be brighter.

I don't intend to alter the protocol, just replace the implementation. Haven't seen anything that would result otherwise. If something does change, it will be small and well documented. New features will add to the protocol when they happen, of course.

@Ciantic Awesome! I did some readup on Typescript yesterday and I think I'm gonna rewrite ensime-node in Typescript for easier use in vscode. Best way forward - I'll do that just 1-1 as quickly as I can, and then we can work together? I think I need to take small steps since I want ensime-atom to use it too so need to work with ensime-node, ensime-atom and ensime-vscode in unison.

As a user expected ensime to shut down when Atom is closed since I started it from Atom. I expect the ensime-server lifecycle to be managed. Leaving processes running without my knowledge is not obvious. At the very least it should be documented clearly otherwise that the user is expected to shutdown the ensime server themselves.

Other than that I think the approach with a setting that spawns ensime server with or without -Dexplode-on-disconnect would be fine.

What I thought could cause a problem is having sbt launch options (such as -XMX).SBT used to allow you to give it launch options, I stll have a config lying around somewhere however I have no idea where it is

@hedefalk Is there anything outside of ensime that could effect my issue?

@hedefalk I have always had this issue, it always happens when I save a source file. @rorygraves said it was probably a compiler crash (or that that ensime-server wasn’t handling a certain compiler output and was crashing because of it, because it didn’t cause an actual crash)