Allow setting settings by syntax about proton HOT 6 CLOSED

Although it is a bit tricky as we will need to think about where to start applying normal behavior to .

I think that we will always see syntax specific settings of the form .scopename.(text|source).SETTINGS.

UPDATE: nevermind, that isn't always true. I have this in my config also:

".latex.tex.text":
  editor:
    tabLength: 2

Maybe we adopt conventions that if we see a leading . in a config, we have the user set the value as a map. So in my example I could do:

[".latex.tex.text" {:editor {:tabLength 2}}]

or

[".latex.tex.text" {"editor.tabLength" 2}]

Any thoughts?

from proton.

So what proton currently does is, it just takes the config string (`".latex.tex.text") and passes that straight into the atom API for setting a setting.

Yeah we should definitely try to collect all the settings for the user and push it into an array in these cases or something like that

from proton.

Ping, I'm still missing this. Has anyone put any thought into how this might work.

What if we just have a "raw-config" variable people can set in their .proton that we copy/paste directly into ~/.atom/config.cson. It would be totally un-checked and un-verified and would escape the rest of the proton system, but it would give users access to set anything atom can handle.

from proton.

@spencerlyon2 for now you can disable wiping configuration and put configs manually via Settings View 😒 I will try to take care about this issue when will have some time.

from proton.

I think that raw-config thing can be a good short time solution. I'm just worried that people will end up using it for everything 😅

from proton.

Fixed in #169

from proton.