New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add section at end for user's custom preferences #54
add section at end for user's custom preferences #54
Conversation
proper section for users to append their own settings or to override settings in pyllyukko's user.js without having to go through and comment out things every time (im assuming entries with the same name which are later in the file can override settings above them. is that right?)
Good idea.
Not sure.
Yes and no. There might be problems when the user updates the user.js with |
ok i just confirmed that when there are multiple entries of the same name, the later ones override the ones before them. so any user differences could just be appended to the bottom and they will override your settings. |
Ok. Thanks for confirming this. Appending stuff is not the problem, but the |
oh right. yeah i just havent used it like that yet. i wonder what can be done |
We need to look into this. Many users probably has the need to customize stuff, so I think this is quite relevant. |
I'm unable to come up with any quick/easy/clean solution for this. Maybe some Git hackery with customizations in it's own branch...? Dunno. Any suggestions? Because if the |
When using another branch, you also sometimes have to resolve merge conflicts when merging pyllyukko's Another possible strategy: let the user create his own |
moved to #75 |
proper section for users to append their own settings or to override settings in pyllyukko's user.js without having to go through and comment out things every time (im assuming entries with the same name which are later in the file can override settings above them. is that right? if not then oops, i guess it can still serve as a place for settings which arent in pyllyukko's user.js yet or wont ever be)