These are chat archives for ensime/ensime-atom
@Ciantic Awesome! I actually spent yesterday pulling out stuff into ensime-node thingy. I can't really push anything out yet either so I guess we're gonna have to merge our explorations later, but that's ok I think. What's important is learning at this point.
I'm all for typescript, np. I think ensime-node could probably be written in typescript for better documentation of the API and there'll be no problem calling that from ensime-atom using coffescript or ensime-vscode using typescript.
@mdedetrich No, sorry. Comments in ticket. Please try to isolate with really clean state and more focused reports. I haven't been able to reproduce so it's really hard to do much. Issues are definitely server or presentation compiler (SOE and scala.reflect.internal.FatalError in pres. compile), but if ensime-atom provokes it and not ensime-sublime or ensime-emacs, I would very much like to help in nailing what's the provocation.
But please try to create a reproducable instruction from zero state. That's really the big work of nailing these things…
.ensimeearlier this week. The examples are in the
ensime-serversource code under
EnsimeConfigSpecand schema defined in
mkdir ensime-node mkdir ensime-node/spec git mv lib/ensime-client ensime-node git mv spec/ensime-client ensime-node/spec git commit -m "move ensime-client to single folder before breakout" git log --follow ensime-node/ensime-client/client.coffee
This only gives me this single last commit, no history preserved.
git subtree split -P ensime-node -b ensime-node-breakout git checkout ensime-node-breakout git log --follow ensime-client/client.coffee