11 ms·
Atom: Now one step closer to being emacs. Now all you need is a proper text buffer model, instead of the clumsy hack you've got now, and lisp as an extlang. Wai
by qwertyuiop924 11y ago
Atom: Now one step closer to being emacs. Now all you need is a proper text buffer model, instead of the clumsy hack you've got now, and lisp as an extlang. Wait, you already have that because clojurescript. So now you just need better APIs, and a proper buffer model.
While I am a diehard emacs user, I considered using atom for light editing (short enough that I'd want proper highlighting/indent support, but not long enough to get emacs out), but the lack of uniform buffer treatment was a dealbreaker for me. If you can't switch between settings and terminal screens using the same mechanism you switch between text screens with, and it all of the above don't have the same underlying mechanism, than you're doing it wrong.
- SpaceCadetJones 11y agoDo you know of any examples out there on how to write plugins using ClojureScript? I got into Emacs a few months ago, but have been considering switching over to Atom so I can write plugins in CLJS
- qwertyuiop924 11y agohttps://github.com/MarcoPolo/atom-paredit https://github.com/MarcoPolo/atom-paredit I'd also recommend looking at the atom api docs, if you really want to switch.
- SpaceCadetJones 11y agoThank you, this looks like a great minimal yet complete plugin. I'll have to try and hack my own together this weekend.
- qwertyuiop924 11y agoYou're welcome :-D. I'd recommend sticking with emacs though. CLJS is a better lisp than elisp, but emacs is a better platform than atom.