@d6y Gah, that sounds bad. Can you error report with a stracktrace? Should be visible in chrome dev tools… Do you get it when starting server? That uses node's child_process.spawn(). Error sounds like "no directory"… Could be permissions maybe…? Or just bad code :)
About low-hanging fruit. If someone needs any "ui-free" refactorings, that would be REALLY low fruit now. I'm thinking adding a extract variable without any ui feedback would probably be 20 mins of work for me… Is that something someone wants? I don't know if there's anything else that doesn't need ui… Ui is what takes time for me. UI and of course the whole startup issues. Adding features that the server supports already and doesn't need much UI is probably pretty cheap…
@d6y Yes, I use the detached thing. I still need "ensime:start" to start the client though. That command supports starting a server or not depending if there is a port file or not in the project.
The fix I did the other day (yesterday?) probably made it so that server is always stopped if it was started from the current atom window. I think there are feature requests hidden here. You want the power to stop only client sometimes and both other times. Currently there is no way to stop server if it was started outside of Atom. Maybe there is a RPC call that does this?