Bradley Reed wrote:
On Thu, 23 Feb 2006 20:24:24 +0100 (CET)
Pavel Reznicek <[EMAIL PROTECTED]> wrote:
What does "xprop -id 0x1a00041 WM_COMMAND" say?
WM_COMMAND(STRING) = { "Eterm", "", "", "", "", "", "", "", "", "",
"", "" }
There are 2 suspicious issues:
1) The time when it was working right seems to be just before update
from xorg 6.8.2 to 6.9.0 (debian testing).
2) using xprop on "aterm -e top" returns:
WM_COMMAND(STRING) = { "aterm", "-e", "top" }
Let me chime in here. I am not running a quite so up-to-date e16:
$ eesh -ewait version
Enlightenment Version : enlightenment-0.16.8
code is current to : $Date: 2006/01/14 16:27:06 $
but I too have upgraded to xorg 6.9.0 (slackware-current)
Here is what I get:
$ Eterm -e top &
$ eesh -ewait wl
0x140003c : top
$ xprop -id 0x140003c WM_COMMAND
WM_COMMAND(STRING) = { "Eterm", "", "" }
$ xterm -e top &
$ eesh -ewait wl
0x1a0000e : top
$ xprop -id 0x1a0000e WM_COMMAND
WM_COMMAND(STRING) = { "xterm", "-e", "top" }
This is a bug in Eterm CVS. It was ok in 0.9.3.
/Kim
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
