Skip to content
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

Discusion: keep local modification to config easily when upgrading to new version #147

Open
IsoLinearCHiP opened this issue Oct 22, 2012 · 1 comment

Comments

@IsoLinearCHiP
Copy link

Forking off from a discussion started in #118 I am currently testing moving all changes I made to my config's in ~/.config/luakit/ to a seperate file which isn't part of the distribution files.

I'm picking up the suggested name of userprefs.lua and thinking of writing a userprefs.lua.template with examples of some common customizations. I added a pcall'ed require "userprefs" to rc.lua which - if the idea takes on - would then be added upstream.

Additionally maybe also require "plugins" which could consist of a simple table of plugins to be loaded. The rc.conf would be slightly rewritten to look up in said table whether the plugin is to be loaded or not. That way - again - you wouldn't need to touch rc.conf if you only want to enable/disable a plugin. If a plugin isn't mentioned in the plugins.lua rc.conf would just default to upstream's decision whether to load it or not, as before.

So this issue is basically meant for discussion, whether this is a good idea, or a no gains effort. ;)

@c0dev0id
Copy link
Member

c0dev0id commented Sep 5, 2020

This is pretty much the case now. We have userprefs.lua and also :settings. I kind of like the way it is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants