Hi Xavier,
: (btw, when a window is swallowed, i don't see it's name anymore in the WindowList....)
Yup, in essence it's not really a toplevel window when it gets swallowed
by FvwmTabs (it gets reparented to FvwmTabs instead of the root window).
I can see it would be nice to be able to (optionally) have swallowed
windows appear in the windowlist but I don't think this is possible.
[If anyone knows a way I'll be happy to code it up.]
: (pstree -a output)
: | | |-xterm -sl 5000 -bg white
: | | | `-zsh
: | | | `-xtail /tmp/test1
Do you still get the problem if you're not running xtails?
ie. just a shell in an xterm.
I love zsh by the way. :)
: s -10220/287 -10845/-224, g -10215/292 -10840/-219: --- not detected 0x081696f0 'test3'
: s -19934/ 53 -20559/-247, g -19929/ 58 -20554/-242: --- not detected 0x0815eba0 'test2'
: s -14711/226 -15336/-74, g -14706/231 -15331/-69: --- not detected 0x08169f38 'test1'
These messages are output by Fvwm, not FvwmTabs. I don't know what they
mean. They're making me suspicious.
: FvwmTabs: Protocol error: bad 3 (Window); Sequence Number 70
: Opcode (40, 0) = TranslateCoordinates
: Bad resource 60818863 (0x3a005af)
This is suspicious too. But it's an FvwmTabs message. FvwmTabs is trying
to determine the position of a window but the window doesn't exist!
SCoTT. :)
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Wed Feb 04 2004 - 23:41:50 GMT