Teika Kazura said: (by the date of Sat, 23 Oct 2010 16:27:26 +0900 (JST))
> Janek, isn't it overflow from X's 16-bit coordinates? rather not. I have reduced the number of my vievports in order to not exceed the 16bit boundary. Jeremy Hankins said: (by the date of Sun, 24 Oct 2010 09:27:41 -0500) > Janek Kozicki <[email protected]> writes: > > And we have time to debug it. > > Do you still have time? yes, plenty. > > > When X starts, I have following line in my rox autorun script: > > > > xterm -geom 95x15+3520+685 -fg gray -bg black -T last -e watch -n25 "last > > | > > grep -v -e \"janek *pts/[0-9]* *:0.0\"" & > > > > It shows me last logins, except for me logging to X. The window is > > titled "last", due to `-T last` argument. > > Does: > > (get-window-by-name "last") ja...@atak:~$ sawfish-client sawfish 1.6.3.1, Copyright (C) 1999-2000 John Harper sawfish comes with ABSOLUTELY NO WARRANTY; for details see the file COPYING Enter `,help' to list commands. user> (get-window-by-name "last") () user> > > Give you anything, from sawfish-client? That should retrieve the window > if sawfish is managing it (even if it doesn't show up in the windows > menu). If it does return a window you could try: > > (display-window (get-window-by-name "last")) > > > 0x3000024 "last": ("xterm" "XTerm") 574x199+2+18 +-22078+703 > user> (display-window (get-window-by-name "last")) () > Does the location change as you change viewports? I presume that that's > what the "+2+18" is. so it seems that sawfish for some reason stopped managing it. > > I don't know what else should I/can I do. > > > > The goal is to eliminate this behaviour in sawfish ;-) > > Yes... :P I rarely restart my workstation, so we can have even few months to track that down. Given that my GPU won't screw up (which happens roughly every six months of uptime). -- Janek Kozicki http://janek.kozicki.pl/ |
