Hi,
On Thu, 21 Dec 2006 18:47:25 +0100, csant <[EMAIL PROTECTED]> wrote:
with the last pull the focus model kind of completely broke,
The new fix fixed this issue - many thanks :) But...
...unfortunately some keybindings stoped to work. I have the following in
cfg_tiling.lua:
defbindings("WTiling", {
bdoc("Split current frame vertically."),
kpress(META.."S", "WTiling.split_at(_, _sub, 'bottom', true)"),
bdoc("Go to frame above/below/right/left of current frame."),
kpress(META.."Up", "ioncore.goto_next(_sub, 'up', {no_ascend=_})"),
kpress(META.."Down", "ioncore.goto_next(_sub, 'down', {no_ascend=_})"),
kpress(META.."Right", "ioncore.goto_next(_sub, 'right')"),
kpress(META.."Left", "ioncore.goto_next(_sub, 'left')"),
submap(META.."A", {
bdoc("Split current frame horizontally."),
kpress("S", "WTiling.split_at(_, _sub, 'right', true)"),
bdoc("Destroy current frame."),
kpress("X", "WTiling.unsplit_at(_, _sub)"),
}),
})
Well - the META.."Up" and META.."Down" bindings stopped to work in my
horizontally split frames (Left and Right still work fine...). They were
working before the very last pull. I am a bit confused about whether this
is a new regression in the latest darcs pull, or some misconfiguration on
my side that now became more evident. Any hints are welcome :)
/c
