Clojurians Log v2

@jessejanderson: you need to start atom from the terminal to correct the path to iex

that's a problem with atom sadly

Ahh, k - thx.

@geksilla: really like that golden ratio plugin :simple_smile:

@dvcrn thanks!

@dvcrn: I'll try to compile a list if it's helpful.

to be fair, a number of the issues I've come across are limitations of the packages available on atom vs the ones on emacs, not specifically proton itself

do I have to upgrade Atom manually while using Proton? what about individual packages?

If I want to disable pep8 and use flake8 instead, how do I go about doing so in .proton?

the second part is easy - just add the package, but I'm not sure how to disable pep8 checks

Maybe ["core.disabledPackages" ["linter-pep8"]]

nope

Oh, maybe not based on @dvcrn's comments on how disabledPackages works

So the linter-pep8 package has an ignoreErrorCodes array. You could add all the error codes to it.

Doesn't seem like a very good solution, but it'd work

Of course, it'd still be running in the background, which is also annoying

yea, I'd rather avoid it being called at all by proton

@dvcrn: So there is no way to disable core packages?

So for package settings - I’m supposed to do those in my dotfile, right? And ignore the normal Atom Package Settings section?

@jessejanderson: yes

for example, https://github.com/kmoe/dotfiles/blob/master/.proton#L100

Is there an obvious place to find what options are available for a package?

My workflow is currently to set the package settings in the GUI as you're used to doing, then look at my Atom generated config file

you can also go to the console and type atom.packages.config.defaultSettings

(credit to austincrft :simple_smile: )

ahhhh, nice! Thanks.

@austincrft: ended up changing the path that linter-pep8 looks at for pep8 to /bin/true. Still tries to run it, but a least its a simple solution

That also seems hacky, but it's better than writing all the error codes.

yea

it'll work until dvcrn tells us the right way / makes a right way :simple_smile:

is there a right way to specify multiple settings in a single expression? like

["a.b.c" 
    ["d.e" "val"
     "f.g" "val2"]]

In that instance, a.b.c is a package name?

This doesn't seem to work for me

;; appearance
    ["editor" [["fontFamily" "Source Code Pro"]
               ["showIndentGuide" true]
               ["showInvisibles" true]
               ["fontSize" 12]
               ["softWrap" true]]

But I think that's what you were getting at

thats what was getting at

uhg keyboard

on another note - atom seems to keep its process running hogging as much cpu as possible if you start it in a terminal and later close it

not sure if that's proton or atom though

I'd argue that it isn't much better, though. The .proton file seems to be modeled in a way that you don't have to be familiar with clojure to modify it

that's true, but it's a nice-to-have :simple_smile:

Which is also (I assume) why parinfer is disabled in the .proton by default. It would mess with the formatting.

ah good point

Yeah, I think it'd look better from a clojure standpoint, but the current formatting is more straightforward

Now that I think about it, I have this line in my dotfile: ["minimap.plugins" [["git-diff" true] ["pigments" true]]]. I'd be willing to bet that this isn't working. 😛

hehe

Yeah, changing it to

["minimap.plugins.git-diff" true]
["minimap.plugins.pigments" true]

wow that's really weird. when I start atom from term, I get 100% cpu usage for as long as that term is open. Closing it fixes it, and has no effect on atom...

That does seem pretty strange. I'm not experiencing that at all. What OS are you on?

ubuntu 15.10, using zsh.

Hm. I don't have a linux machine next to me right now to test, but I don't experience that on Windows or OSX

odd

it may be zsh specific

That's possible. Mine sits at 0% and only spikes to about 0.5% when typign

so when I run xterm bash then run atom inside it, it seems fine

Hm. I'd be interested in what zsh is doing with the process.

not sure how to test that - maybe whatever atom uses to start the gui from the command line has an issue with zsh?

It's basically just running a modified version of chromium

that I get - i'm not sure how to check what zsh is doing differently that bash when it starts stuff though

You could try running the chromium executable from zsh to see if it's specifically an incompatibility with Atom

If it's an Atom thing, I'd report it to the Atom repo. If not, report to the zsh repo if there is one?

I know admittedly nothing about zsh other than it's a shell alternative. 😛

I'll look into it more tonight. Not really worth stressing over it atm since I have work to do 😛