On Wed, Dec 19, 2007 at 02:09:33PM +0100, David wrote:
> Joerg van den Hoff <[EMAIL PROTECTED]> writes:
> > mod1+return does *not* open new xterm. only mod1+a shows the
> > "exec, quit, welcome" etc. entries in the menu, which I  can
> > select (e.g. quit) but which perform no action.
> >
> > so wmii seems to run but seems semi-conscious at best :-).
> 
> Make sure you don't have any old configuration files from wmii-3.1 lying
> around. It should all work if you do a clean install of 3.6.

I did move the old ones (~/.wmii-3) out of the way (although
the new ones are in  a  separate  destination  (~/.wmii-3.5)
anyway?),  but to no avail. 

I  had  already  done  chmod -x for the old (still existing)
wmii-3.1 which resides in a separate tree (maintained by the
`macports'    system) that is further up in the search path.
I now did the same for any old wmii* executable which I  had
overlooked before. this has a small effect:

now  the  dmenu  at  the bottom shows some effect: selecting
"exec"  or "quit" quits the X session.

apart  from that: same behaviour as before: single maximized
xterm (which starts up prior to wmii in .xinitrc) with empty
title  bar  (no tags or window titles or whatever indicated)
and a (black) task bar at the bottom in which  after  mod1+a
the  (dmenu?)  entries  occur.  nothing else has any effect.
clicking in the title bar with  the  mouse  (yuck!)  pops  a
small menu ("Nop; Delete; Fullscreen") where again selecting
any entry does not cause any action.

starting  `xterm'   from the command line does popup the new
xterm behind the primary one (again maximized).  (I  checked
this  using "nohup xterm &" and quitting the primary xterm.)

it  seems that the wm is running but anything related to the
wmii resources is not recognized  althought  the  files  are
there  (I  test-installed  everything in a separate tree and
all the subdirs/files seem to be threre and OK.)

> 
> > is  `dmenu'  of  importance  at  this  stage?  (I  only have
> > dmenu3.2 installed).
> 
> Since you see the "exec, quit, welcome" menu it seems to work.
> 
> -David
> 
> 

any more ideas? I'd love to get it to working correctly.

one  idea:  is there a danger of some hidden collisions with
the  old  (still  existing)  wmii-3.1  installation?    libs
installed there might be used by gcc/ld, but I think this is
quite OK (and I don't know, which non-system libs wmii needs
except libixp). just to give the complete picture.

joerg

PS: thanks for taking the time

Reply via email to