This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aatree (3)
- # announcements (1)
- # architecture (5)
- # beginners (27)
- # boot (22)
- # cider (17)
- # cljsrn (8)
- # clojure (93)
- # clojure-canada (1)
- # clojure-dev (7)
- # clojure-nl (10)
- # clojure-poland (216)
- # clojure-russia (35)
- # clojurescript (163)
- # community-development (6)
- # cursive (25)
- # datavis (6)
- # datomic (18)
- # dirac (10)
- # dysphemism (4)
- # editors (3)
- # editors-rus (1)
- # emacs (15)
- # hoplon (124)
- # instaparse (25)
- # jobs (10)
- # ldnclj (78)
- # lein-figwheel (11)
- # leiningen (6)
- # off-topic (20)
- # om (149)
- # onyx (2)
- # parinfer (5)
- # portland-or (1)
- # proton (62)
- # quil (2)
- # re-frame (8)
- # spacemacs (4)
- # yada (20)
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
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
linter-pep8 package has an
ignoreErrorCodes array. You could add all the error codes to it.
So for package settings - I’m supposed to do those in my dotfile, right? And ignore the normal Atom Package Settings section?
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
@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
is there a right way to specify multiple settings in a single expression? like
["a.b.c" ["d.e" "val" "f.g" "val2"]]
This doesn't seem to work for me
;; appearance ["editor" [["fontFamily" "Source Code Pro"] ["showIndentGuide" true] ["showInvisibles" true] ["fontSize" 12] ["softWrap" true]]
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
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
Which is also (I assume) why parinfer is disabled in the
.proton by default. It would mess with the formatting.
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. 😛
Yeah, changing it to
made it work. I'm surprised I didn't notice it wasn't working. 😛
["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?
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
not sure how to test that - maybe whatever atom uses to start the gui from the command line has an issue with zsh?
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?