On Sat, Jan 27, 2007 at 01:20:55PM +0100, csant wrote:
> On Sat, 27 Jan 2007 01:32:49 +0100, Frederik Eaton <[EMAIL PROTECTED]> wrote:
> >These questions have been answered on IRC. thanks
> It would be nice if you could in any case post them to the list as well - so
> others will have an easier way to find the
> answers (and they do not have to be repeated once again on IRC).
>
> Thanks,
> /c :)
Summary: "mod_ionws has been renamed to mod_tiling"
"Maybe one or two keybindings need fixing as well."
22:19 < _frederik_> hello, i've upgraded ion and now it isn't working again
22:19 < _frederik_> do i have to change something about my configuration?
22:19 < _frederik_> version is 3ds-20061223
22:20 < _frederik_> there are no tabs at the top of the screen
22:50 < urs> _frederik_: what version did you upgrade from? pre-october?
22:57 < waawaamilk> _frederik_: what happens if you create a new workspace? do
things work there?
23:07 < _frederik_> urs: yes, certainly
23:07 < _frederik_> waawaamilk: if i create a new workspace, it comes up
floating
23:11 < waawaamilk> can you not get a query for one?
23:11 < _frederik_> query?
23:11 < waawaamilk> F9
23:11 < urs> _frederik_: the most important config-change from pre-december
versions is that mod_ionws has been renamed to
mod_tiling
23:12 < _frederik_> urs: oh
23:12 < _frederik_> urs: perhaps that's the issue
23:12 < urs> So you'll need to fix that in your config
23:12 < urs> Maybe one or two keybindings need fixing as well.
23:12 < _frederik_> why are there so many incompatible changes?
23:12 < urs> Because the internal architecture has been overhauled an (imho)
beautified.
23:13 < _frederik_> sure, but renaming things isn't important enough to be a
reason to break compatibility
23:13 < urs> The new code doesn't differentiate between tiling and frame
workspaces anymore, you can mix them freely.
23:13 < urs> Well, ion has always been a development playground. If you want
stability, stick with ion2. :)
Here's a description of the changes I made, using the above hints:
$ diff -u .ion3/cfg_ion.lua{.orig,}
--- .ion3/cfg_ion.lua.orig 2007-01-26 22:36:33.000000000 +0000
+++ .ion3/cfg_ion.lua 2007-01-26 23:29:57.000000000 +0000
@@ -30,7 +30,7 @@
warp=true,
-- Default workspace type.
- default_ws_type="WIonWS",
+ default_ws_type="WTiling",
}
@@ -41,9 +41,9 @@
-- Load some modules.
dopath("mod_query")
dopath("mod_menu")
-dopath("mod_ionws")
-dopath("mod_floatws")
-dopath("mod_panews")
+dopath("mod_tiling")
+--dopath("mod_floatws")
+--dopath("mod_panews")
--dopath("mod_statusbar")
dopath("mod_dock")
--dopath("mod_sp")
Also, I had to change .ion3/cfg_bindings.lua, inserting the following
blocks (taken from the new /etc/X11/ion3/cfg_bindings.lua) and
removing the corresponding bindings from their old locations:
----------------------------------------------------------------
-- Client window bindings
--
-- These bindings affect client windows directly.
defbindings("WClientWin", {
bdoc("Nudge the client window. This might help with some "..
"programs' resizing problems."),
kpress_wait(META.."L", "WClientWin.nudge(_)"),
submap(META.."T", {
bdoc("Kill client owning the client window."),
kpress("C", "WClientWin.kill(_)"),
bdoc("Send next key press to the client window. "..
"Some programs may not allow this by default."),
kpress("Q", "WClientWin.quote_next(_)"),
}),
})
-- Client window group bindings
defbindings("WGroupCW", {
bdoc("Toggle client window group full-screen mode"),
kpress_wait(META.."Return",
"WClientWin.set_fullscreen(_:bottom(), 'toggle')"),
})
----------------------------------------------------------------
Best,
Frederik
--
http://ofb.net/~frederik/
