On Thu, 2 Aug 2007 11:42:35 -0400 Etan Reisner <[EMAIL PROTECTED]> wrote:
ER> On Thu, Aug 02, 2007 at 08:37:21AM +0200, Andreas Bernauer wrote:
>> Etan Reisner schrieb am Di, 31. Jul 2007 um 13:58 (-0400):
>> > > Copy /usr/local/etc/ion3/cfg_tiling to your ~/.ion3 and modify it.
>> >
>> > No, do not copy random system files into ~/.ion3 only copy cfg_ion.lua,
>> > cfg_statusbar.lua, and cfg_dock.lua. Leave the rest in the system
>> > locations and override the bindings in cfg_ion.lua or in any other file
>> > you want as long as you dopath("") it from cfg_ion.lua.
>>
>> Could you give me any special reasons for your suggestion, just out of
>> curiosity?
>>
>> Andreas.
ER> Short version: Easier to maintain across upstream changes.
ER> Long version If you copy the entire cfg_tiling.lua into .ion3 and then a
ER> function name changes your carefully copied and modified version will be
ER> broken. And you will have no idea why. Essentially you become forced to
ER> watch the changelog very carefully and diff your version against the
ER> system version after each new release. If, on the other hand, all you do
ER> is create secondary config file (e.g. cfg_my.lua or my_tiling.lua) then
ER> when versions change you only need to worry about changes to the bindings
ER> you have actually customized (and perhaps any newly added system bindings
ER> that take precedence over yours, but that is much easier to notice and
ER> fix). Unless you intend to change the majority of the existing bindings it
ER> is, as far as I have ever been concerned, a net loss to copy the system
ER> files in.
I'd just like to point out that this is exactly why the Ion
configuration should not be in Lua and subject to change any time an
update comes down IMO.
Something like this:
META.."S" = split_here_horizontal
META.."V" = split_here_vertical
Is all 99% of end users need. Wouldn't this be easier for everyone?
Maybe it could be a module...
Ted
