I've put up a vscode-clover repo with my current VS Code settings, key bindings, and the Clover config.cljs (the latter is identical to the chlorine-config.cljs file in my atom-chlorine-setup repo mantioned earlier). This encouraged me to install VS Code over the weekend and, sure enough, every single piece of my Atom/Chlorine setup works out-of-the-box with VS Code/Clover, and I was able to use the exact same key bindings that I'm used to from Atom! The only downside is that the tasks don't show up in the VS Code "Command Palette" so they're not as discoverable. The other day on Slack, however, Mauricio announced that he had been able to port the ClojureScript-based extension machinery from Chlorine to Clover for VS Code, and the customizations are surfaced as "Tasks" that can be run via the VS Code API and which can have key bindings associated with them. Microsoft owns GitHub, which produced Atom and Electron, but has the wildly successful VS Code which is where most of the attention is. The State of Clojure 2020 Survey showed VS Code usage climbing to 10% this year (from 6.6% last year) while Atom usage dropped to 3.9% (from just over 4.5%). Level of love and support (not from Clojurians themselves, nor from the company behind them). VS Code, despite feeling that Atom isn't really getting the same Roadblock has been that VS Code doesn't allow you to add newĬommands at startup via the sort of user-supplied init-file VS Code that provides the same core functionality, but a potential With the latter being in its own repl-tooling repo.īased on this separation, he's been working on an extension for Such a way that the editor-specific functionality was separateįrom the core REPL management and evaluation functionality, One of Mauricio's goals with Chlorine was to structure it in Mauricio Szabo has done on Chlorine, adding a way toĮxtend the functionality using ClojureScript
I've been very impressed with the work that Where I initially used ProtoREPL (which is no longer maintained)Īt the end of 2018. I've written before about how I switched from Emacs to Atom
0 kommentar(er)
