I will re-add them then until we really need space for more command categories

@geksilla: are you around?

yes

sorry for asking again - how could I use your doc helper?

require proton.lib.doc_helper

I mean - where are you running it from? The repl?

and call proton.lib.doc_helper/layer-packages-configs-doc-table :tools/git

yes from the repl

this method returns string

so you can output it to browser console or to terminal

like

(prn (proton.lib.doc_helper/layer-packages-configs-doc-table :tools/git))

hmm it seems to not generate for all the keybindings 😞

it generates configuration for packages

not keybindings

ohhh

)

ok got it

thank you

np

if I have time I will try to write one for keybindings

ok cool!

i thought that we can use such functions to generate markdown convert it to html and show to user

that would be cool too yeah

in general I want to readmes to be automatic if possible

put all the help text inside the layer and generate the readmes from that

but that’s long term plan

not that urgent

yes

agree )

I will merge your doc helper into master

ok

also want to add few packages to category applications under SPC a https://atom.io/packages/ask-stack https://atom.io/packages/imdone-atom https://atom.io/packages/atom-pair

what do you think about it?

sounds good to me. But should definitely be in separate layers

yes

package per layer

like :apps/pair-programming, :apps/imdone, :apps/stackoverflow

it’s scary how much you get used to parinfer

I am using spacemacs right now because I couldn’t get proto-repl working and have a problem with brackets lol

)))

parinfer ident mode is awesome

should I split the commands by category?

something like that

hmm I think we should maybe generate the title…

:g :b :c for example. We already have all the information of how to construct the title except the last action

:g -> git :b -> branch :c -> checkout => git branch checkout

copy and pasted that into the git readme https://github.com/dvcrn/proton/blob/feature/git-keybindings/src/cljs/proton/layers/tools/git/README.md

Ok let’s see…. - Keybindings: We can generate - Options: We can generate as well - Package list: Should be no problem. Just construct the URL with http://atom.io/packages/{{package-name}} - Install instructions is a no brainer Just the description missing and we can pump out READMEs

Awesome!

just the doc helper needs some refactoring

I’m not happy about my function

wow that pair programming thing looks nice

I wonder if writing a repl client against 1.8's socket repls might be easier than nrepl? anyone looked into that?

With some better REPL integration atom could become really nice.