@lilactown I think I have a fix. Will try on a mac computer today and deploy a new version. Unfortunately, Chlorine now is a mix of one single JS file and the rest are ClojureScript ones. I also have absolutely no idea why this approach fixes MacOSX code, and why the bug happened in the first place - the thing is so bizarre that I don't even know how could I explain the bug to be able to file a bug report to Atom team... I'm making some tests to be sure that nothing changes (compile should refresh the Atom package and re-register commands, all commands that Chlorine support now need to run exactly the same way) but so far, things seem to be working.
😩 sounds miserable. Thanks for all the hard work! I’m willing to give it a whirl as well to help with testing