Hmm, didn’t work.

huh? let me try

haha the real proton is killing it

Probably need to add it to my packages list

ah you have to of course put :proton inside your dotfile 😛

Yeah, not working for me still

hrrmm

I’ll just roll back to an old commit of one of my other packages

ah this works @sglyon :

go into ~/.atom/packages/<any-package>

change the version inside package.json

nice

/tmp/proton/plugin
λ apm outdated
Package Updates Available (1)
└── vim-mode 0.62.0 -> 0.63.0

Oh geez I don’t want anything to do with that json output though

maybe a regex match from ── to a number or something

I mean the json isn’t so bad

it is an array of json objects, each of which has a name field

I can skip the rest of it

Is there a way to turn this stdout into a vector of maps?

(.parse js/JSON) to get an object and js->clj to convert it into a clojure map. Though david nolen mentioned before that it would be better to use goog libraries for dealing with js objects instead of converting them to clojure

I’m happy to leave it as json as long as I can ask the json what name is for each object in the array

try js/JSON then

wait… can I access the proton ns/commands from the devtools?

That’d be killer

maybe from the REPL but from the devtools console, no

I’m seeing them now

(they tab complete)

proton.lib.package_manager.get_apm_path()
"/opt/homebrew-cask/Caskroom/atom/1.1.0/Atom.app/Contents/Resources/app/apm/bin/apm”

That came from the atom devtools console

oh lol

how did you compile it?

I’ve got a lein run -m build/dev-repl process running right now

So all the stuff is already js (no more clojure), but I can still interact with it

maybe because it is not optimized? @thheller can answer that probably 😛

Didn't know that was possible

Not sure, but I’m pretty happy it is possible

Nice

JSON.parse worked — gave me an array of json obejcts

anything useful in there?

Yeah

proton.lib.package_manager.child_process.exec(proton.lib.package_manager.get_apm_path().concat(" outdated --json"), function (error, stdout, stderr) {
    var json_stdout = JSON.parse(stdout)
    var names = json_stdout.map(function(x){return x.name;});
    console.log(names)
});
> ChildProcess {domain: null, _events: Object, _eventsCount: 2, _maxListeners: undefined, _closesNeeded: 3…}
>  ["vim-mode”]

Now I just need to figure out how to return that names variable

Ahh is that what the channel is for in the install and remove package methods?

well there is also execSync, but I used a channel because otherwise each installation would block the entire editor

now it's async so it executes and we just pull the result of that execution back and display it

That’s very nice. I think I’m close

in theory just pipe it into the channel, close it and you should be good

I'm going for lunch, will be back in 1h ish

quick question?

sure

I’ve got the array of json objects

now I want to do something like this:

(map #(.name %) (.parse js/JSON stdout))

where I was hoping the .name would give me the name field on that json object, but it didn't

How should I access that field?

to access properties, you have to use (.-name %)

.- is the interop for that

http://www.spacjer.com/blog/2014/09/12/clojurescript-javascript-interop/

ok cool

success!

So can I shove the result of that map into the chan?

yep, or use the execSync version if it's fast enough for non async

Last question, how do I get it out of the chan?

(defn outdated-packages-chan []
  (println "finding outdated packages")
  (let [c (chan)]
    (go
      (.exec child-process "apm outdated --json"
        (fn [err stdout stderr]
          (if (nil? err)
            (do
              (println (str "The json is here: " (map #(.-name %) (.parse js/JSON stdout))))
              (go (>! c (map #(.-name %) (.parse js/JSON stdout))))
              (close! c))
            (do
              (go (>! c false))
              (close! c))))))
    c))

especially if you never used core.async it might be a bit tricky to understand 😛

Haha i’ve never used clojure...

(<! channel) is for pulling out of a channel, put in cljs you can only use it inside a go block which is also a channel

so instead of that c at the end should I just do (go (<! c)) to return the actual list of package names I want?

so you have to do something like

(go 
   (let [result (<! mychannel)]
    (println result))

no, (go) is also returning a channel

ahh

you can't really return a value out of a go block. If you work with async, just put it inside the channel that you return (`c` in that case) and let the receiving part just pull that value out of it

oooor use the execSync version 😛

haha — I’m determined to learn the async stuff

really fun stuff, but also not that easy to grasp

I also have a lot of problems with it

I’ve seen these concepts in go

But haven’t done a ton with them

what about returning (<!! c)

takes a val from port. Will return nil if closed. Will block
if nothing is available.

that's clojure. You can't use that in clojurescript

in cljs everything has to be inside a go block

<!! is for real threads afaik which we don't really have in cljs

ok

Oh I think I see what to do

return the channel

check out this talk - very cool! https://www.youtube.com/watch?v=enwIIGzhahw

Then have my update-packages command just call the apm update methods from within a go block?

well if you copied my code then update-packages is also a async operation that uses channels. So calling update-package will give you a channel back

but yeah that should work. But feel free to experiment a bit around with it

Ok thanks

what helps me understand is that everything inside a go block is getting executed async

Pretty cool stuff

high recommendation for that talk up there. It's more clojure stuff but very cool

now going for lunch 🍞

But it’s about time for me to call it a night, so I might balk and just do execSync

sure!

This is a single call, so async doesn’t earn us anything (I think)

well I think atom is doing some requests to the repository though so it could take a while

I could rewrite it later on in async if you want

if you get the sync version up

That’d be a good way to learn

@sglyon @dvcrn sorry didn't follow the conversation. what was the issue? 😛

No problem. There wasn't really an issue, @dvcrn was just helping me out with some basic stuff as I've never used clojurescript or clojure before.

Hi there.

@dvcrn what is the 'proton prompt'?

installed atom via .deb package from their site.

then

apm install proton-mode

after startup proton does some stuff.

that should work

and it still doesn’t work? Open a file and hit space

I see.

Do you have any errors in your console?

nope.

I just tested the store listed version and don’t have problems hmm

works.

oh?

would it be possible to start opening a file with space?

like space f f

like in spacemacs?

so i open a file with ctrl-o.

you mean on initial start?

yes.

that’s on the list We need to get atom somehow to accept our command chain without a editor context

definitely something that should come soon

ah, i see.

if you have a file open though you can do <spc> p f to open the file searcher

so for now e.g. opening files is always with ctrl -o?

ok.

<spc> p r for recents and <spc> b b for buffers is also in

ok.

so does atom have a fuzzy file finder?

just asking, because maybe i can help a bit?

(though no expereience with clojure script)

<spc> f f would use the finder then, i guess?

p f is already fuzzy but if you want something even fuzzier, you can open ~/.proton and replace the OpenFileProvider :normal with :nuclide, though I can only recommend it if you have a medium powerful machine because it does a lot of babel compiling first

always looking for help

Here’s also a doc how to contribute layers to get started https://github.com/dvcrn/proton/blob/master/HOW-TO-LAYER.md

ah, ok.

it’s a fun project to get started with clojurescript

for sure

<spc> _ d opens your .proton file by the way

thanks.

just killed the only buffer, and

<spc>

hrm yeah we definitely should put more focus on getting it work on non buffers

just a couple of questions:

how can i get highlighted search?

I search with "/" and then start typing

input is at the bottom

how can i change themes? I see the line in the .proton file, is it always like ["core.themes" ["theme-ui", "theme-syntax"]]?

ok for the first part, this is a limitation on atoms site but I already have that working on my local machine. Gonna merge that back in and then incremental search and highlights will work

for themes

that is super cool!

add your theme package inside additional-packages and change

["core.themes" ["atom-material-ui" "atom-material-syntax"]]

the first part is the ui, the second part the syntax theme

ok.

by default we use material but to get the default atom one back for example, just change it to [“core.themes” [“one-dark-ui” “one-dark-syntax”]]

if you are not sure about the name, you can also use the package installer to browse themes, change it and open your atom config (in the settings menu) to see how it is called internally. Then just add that to your .proton file

proton will get rid of all the stuff you tested and don’t need on next start

ah, ok! thanks!