chlorine-clover

About Chlorine for Atom and Clover for VS Code: https://atom.io/packages/chlorine and https://marketplace.visualstudio.com/items?itemName=mauricioszabo.clover
seancorfield 2020-05-22T16:18:43.486600Z

@mauricio.szabo Is there enough of the Atom API exposed in the new cljs extension stuff to be able to rewrite all of this? https://github.com/seancorfield/atom-chlorine-setup/blob/master/init.coffee

seancorfield 2020-05-22T16:19:38.487500Z

I can see how to do the basic command dispatch I think, but I can't see how to do the "maintaining cursor position" stuff...

mauricio.szabo 2020-05-22T17:36:27.489600Z

I don't think so... the config API does not expose the full Atom API (it's not even on the same "context" of Atom, and also on SCI I need to whitelist all methods that anyone will intend to use)

seancorfield 2020-05-22T17:41:04.490500Z

The new cljs stuff can run any Atom command tho', yes? So I think only the get/set ranges part is "missing" and those could be added to the editor namespace perhaps?

mauricio.szabo 2020-05-22T20:22:08.491700Z

No, the new cljs can only run Chlorine commands. The interpreter doesn't even know that it's running over Atom or VSCode or any editor...

mauricio.szabo 2020-05-22T20:23:04.492800Z

The thing is that currently Chlorine "knows" how to do some operations on Atom, like displaying notifications, getting editor info, etc. But these are generic enough to be easily portable to VSCode, for example

seancorfield 2020-05-22T21:59:11.493200Z

OK, that makes sense. Thanks.

👍 1