Clojurians Log v2
proton
@beetlefeet one idea was to not block the editor at all and move the modal into a corner. Though not sure how that would work if you try to use layers that rely on packages that are not installed yet
keymaps and settings are almost instant, the packages are what's taking so much time
Is it the loading or consolidating the installed ones vs the required ones?
it's diffing the installed vs required ones and installs / removes accordingly. The diffing needs almost no time, just the actual installing is really slow
it seems like the ‘splash’ stays up a long time even when there is nothing to remove or install though
and also takes a while to appear in the first place
yep correct because it would almost disappear immediately and make the entire information in it useless. By default it's set to 3s I think but you can change that in your proton config with proton.core.post-init-timeout
though appearing should be instant :thinking_face:
probably just actually loading all the atom packages is the wait before it appears
maybe if all the statuses are “OK” it could just be non-modal and skip the 3s. (or like animate and minimise to a little icon in the toolbar 🙂 that’d be fancy) I’ll try setting that config value...
It works. now I have a pause while apm loads the packages and then a blip of proton. I like the idea of proton not blocking unless there is something interesting (like a new or removed package). I
I’m going to checkout the repo and see if I can understand the clojure enough to have a crack at it.
(zero experience in lisp :/)
it's really quite simple 🙂 learning a lisp like clojure is a very valuable skill to have. You'll learn a lot of things that you can apply to other languages
(not saying proton code is the cleanest though..)
neither is the code I work with everyday 😉
this is the monster init function we are using right now
the last line is setting the timeout
I think the easiest way would be to do something like
(if
(and
(> (count to-remove) 0)
(> (count to-install) 0))
;; show timeout
;; do something else
)
ah, not and 😛
Longest will probably be figuring out how to build and get atom to use my version of proton 🙂 (Any tricks to that, just installing leiningen..) Also would be good to not even show the window even for a blip, that can be a stretch goal 😛
just remove proton from your atom, compile the source with lein and do apm link inside the plugin/ folder
Back from doing actual work… I did that and I see proton-mode in settings > packages and if I ‘view code’ it shows the code in /plugin/ directory of the local repo correctly. But no proton loaded and no proton stuff in the command palette. Just wondering if that is something you’ve seen and fixed?
oh, there’s no javascript files in /plugin/ I did ‘lein compile’ but I guess it didn’t work
Don’t mind me, I managed to completely miss the command to run in README, now just trying to update JDK...
🙂
Proton seems to have broken just now. Anyone else have the same issue?
Are you on 0.13.2 of proton-mode?
ugh I switched computers so idk atm, but I have not manually updated anything almost vanilla setup I just disable parinfer and install paredit
in my config
I actually had a working instance of atom running the new ones are the ones that break. I remember the errors have todo with deprecations
Atom 1.13.0 broke proton and then proton 0.13.2 fixed it. So if you update atom and proton to newest it should be working.
@kidpollo yeah probably need to wait for auto-update to trigger