Clojurians Log v2

it was a variation with big tabs before but we reverted it. Most people seemed to prefer smaller tabs The ideal solution would be to not have tabs at all and treat open tabs like buffers like in other editors. You navigate with SPC b b + SPC tab and fuzzy jump between open files

though most people didn't get that 😛

@bazzy has joined the channel

Hello, fellow protonists 😉

hi

Please, help me to resolve configuring issues with proton. How I should write proton config statement, that tranforms to that block in config.cson:

".clojure.source":
  editor:
    tabLength: 1

hmm

let me see

@bazzy: you would probably have to do something like [“.clojure.source.editor.tabLength” 1]

Let me check

Nah, doesn't work. It transforms into the:

"":
    clojure:
      source:
        editor:
          tabLength: 1

hmm

yea looks like this is a problem then, you have an edge case

I would ask @dvcrn or open up an issue

I'm surprised, because any clojure-language package configs should be written in that ".clojure.source...." form

How do you guys reconfigure those defaults for clojure-language?

yea not sure, not exactly the pro here

hrrm I'm pretty sure we had this problem before

ping @geksilla

I knew we had that before!

@bazzy, @spectre: use

["editor.tabLength" 2 {:scopeSelector [".source.clojure"]}]

https://github.com/dvcrn/proton/pull/169

@dvcrn Thanks a lot, it helps 👍

@bazzy: no problem! You can use the scopeSelector as well to apply the same options to multiple scopes. Just add them to the array

I'm using Proton with Atom 1.11. It was too slow to use before that. Great work done with Proton by just a handful of you guys. Much appreciated 🙂

@dvcrn: Can I create private layers in proton like in spacemacs?

@ikhthiandor: yes and no. You can’t put them into a directory and let proton read it because clojurescript is a compiled language. But you can clone fork+clone the project, create a new layer and run lein run -m build/release and it compiles it with your newly created layer

ok. thanks for clarifying

that is the goal, yes

but last time I checked bootstrap cljs was still too new

yeah. Having an atom setup for it would be awesome though. I saw that proto-repl has a self hosted cljs repl, but it is unclear how useful it is yet

if you have experience with it, please. We could definitely need that knowledge 🙂

haha, I hacked replumb to let me use the compiler piece rather than just eval in the browser, but I barely understood how I actually got it working

it would already help a lot if we could turn .proton from edn into a real cljs file that allows anonymous function definitions. if we read that with bootstrap and get the functions to be useful it would be huge

we could start shifting more power into .proton like allowing keybindings to directly execute anonymous functions that receive some of the atom context (like workspace, etc). That would be the first step in direction “private layers"

@ikhthiandor: how much of a speed boost are you noticing with atom beta vs atom? I definitely notice that the space menu opens up and move a lot faster, and some of the UI just feels a lot faster