nigeltao/taowm

The Acutely Opinionated Window Manager

taowm's Issues

Can't get taowm to start.

I'm trying to see how taowm compares to awesome or ion, and I can't seem to get it to start. When I add it to the end of my .xsession, it immediately quit with no error message and nothing obvious in the X server logs. I've tried putting it in a menu option and to it from pwm in the same way that other WMs are options that can be switched to (and work), but again, it seems to just quit back to the terminal. No panic, no error message, nothing. It seems like it's just exiting (and then X is exiting as a result.)

It's not very helpful, but this is my .xsession file, since I can't find any other useful information (both the rio and pwm options work.)

PLAN9=/usr/local/plan9 export PLAN9
GOPATH=/home/driusan/Code/Go
PATH=$PATH:$PLAN9/bin:$GOPATH/bin export PATH

xmodmap ~/.Xmodmap
xclock -geom 128x128-0+0&
# exec rio
# exec pwm
/home/driusan/Code/Go/bin/taowm

how to find the who create this window

@nigeltao

Hi Nigel,

I have used your wm for a long time, just amend it slightly for myself. I like it a lot.

Now I encounter a problem sometimes. If I open one application, but it doesn't map its window immediately due some reason. If I change to another workspace now and the new window will belong to the current workspace. This is because in the code, it use the current frame to determine the workspace when a new window map.

But I just want the new window belong to its original workspace that creates it.
I try to use window's parent but it's not the key... Do you have some ideas?

Hope I explain clearly, It just like follow:

in workspace A: sleep 10 && startNewWindow
and I transfer to workspace B
then the new window is located in workspace B, but this is not expected...

osx

osx does not support xsession from what i have found googling around.
Any ideas ? Would like to try this out and see how it feels. Its a good idea.

Do you use this when developing ?