You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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. ;)
The text was updated successfully, but these errors were encountered:
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. ;)
The text was updated successfully, but these errors were encountered: