proton

https://github.com/dvcrn/proton
beetlefeet 2016-10-06T07:08:27.000090Z

Long shot: anyone written or know of anything that can help quickly populate a bunch of .proton config options from a ‘legacy’ atom config.cson?

dvcrn 2016-10-06T07:14:14.000091Z

Good idea but no doesn't exist yet

dvcrn 2016-10-06T07:15:19.000092Z

It would be as simple as just taking a cson parser and spitting out edn. I'll give it a try if I have some time

beetlefeet 2016-10-06T07:25:34.000093Z

Cool. PS hi dvcrn! Thanks for proton! loving it so far - just found it this morning. I’d made a spacemacs-evil-keys atom package for myself but will be moving wholesale to this I think 🙂

dvcrn 2016-10-06T07:26:32.000095Z

great to hear 🙂 thank you

beetlefeet 2016-10-06T08:41:26.000096Z

Ok another question while I try to set things up 🙂 I want to add a bunch of new keybindings (not keymapping) to SPC etc etc. IE SPC f y which will trigger "editor:copy-project-path”. But it seems that adding that into .proton doesn’t work. The example is that you can run ‘Hello’ but what is that? I think maybe the ‘actions’ that keybindings resolve to is different from the 'commands' you can run from keymappings and from the command palette? Or is it something around having to create a layer to house my bindings like those?

beetlefeet 2016-10-06T08:49:03.000097Z

Looking at the layers the actions seem to just be in that format of package-name:command-from-command-palette. I guess you just can’t do so much from outside of a layer?