Well, to be honest I just didn't implement it yet, but I'm not really against typing on the REPL. Its just that, as Sean mentioned, it's not that big deal to me too. But I'll look into it.
By the way, I'm thinking about adding some -beta
commands on Chlorine. There are lots of things that I want to test (like a way to detect start/end of forms without relying on Atom editor's internals) that aren't still stable yet, but I'm afraid this could slow down Chlorine's publication of newer versions
(but that I also want to be able to test on my day-to-day workflow to catch bugs too)
Good idea! Testing “in production” is a solid approach when approached thoughtfully. In terms of ergonomics, it might be slightly better to have a single config switch “enable experimental features” that would enable whatever is half-baked, and perhaps if it’s off they wouldn’t show up in the list of commands. I don’t know if Atom’s infrastructure makes this possible/practical but if so it might be worth considering.
The config approach is something I didn't consider, but I think it's even better! After all, people won't need to rebind keymaps.