Z It would appear that on Mar 21, Carsten Haitzler did say: > On Tue, 20 Mar 2012 13:36:53 -0400 "Joe(theWordy)Philbrook" <[email protected]> > said: > > > > > Perhaps Konsole *_IS_* broken. Though I think it's more like KDE4 has the > > foul smell of much broken{wind}. And I suspect that this aspect of whatever > > Konsole is doing wrong so that xprop doesn't get the full command string > > has been happening for some time now. I didn't start using E17 till kde4 > > ticked me off. But I've never been able to use windows remembers to > > start one of these konsoles "on login" complete with the path, profile, or > > executable... Also the WM_COMMAND(STRING) doesn't include the argument list > > even when I start it from within E Like with the keyboard shortcut. Nor > > does it when I run xprop when running any of the other 4 installed Linux > > distros {with all of which, the window "name" is still correctly assigned > > even when initialized via ~/.xinitrc...} It's like Konsole uses the CLI > > options, but doesn't see any reason to share the info. > > thats what it smells like. i use xterm and it behaves like a good little boy: > > WM_COMMAND(STRING) = { "xterm", "-e", "htop" } > > > > > However I did find that once I "created a personal launcher" for the > > > > bash script, the launcher showed up in the "StartUp Applications" dialog > > > > Which does successfully start both konsole windows with ALL their > > > > correct > > > > values {including unique window names} Allowing the "Window Remembers to > > > > work with the more stable name/class recognition values. > > > > > > > > So for me it's no longer an issue. > > > > > > cool. well at this point the only other thing i'd say is.. "don't use > > > konsole if its broken". xterm i know works correctly (with some .Xdefaults > > > it looks just fine color and font-wise).
I note: that the above behavior had trickled down though ALL my installed Linux so that I'd had to define those personal launchers and set them as startup applications instead of calling the konsole instances in my ~/.xinitrc files if I wanted the --name command option to work properly with all of my installed Linux... Then suddenly today: Sun May 20 2012, I don't know what changed. But I just updated both my Sabayon and my Arch linux distributions. And in both cases I the --name options in the script called by the personal launchers no longer assign a unique NAME value to the two Konsole windows... But the kicker is that in both cases all I had to do was to delete the personal launchers && uncomment the old konsole command lines in my ~/.xinitrc to again be able to use the "NAME" ICCCM property in the windows remembers dialog... And in fact, since I'd already learned this with my Arch installation before I fired up e17 in my updated Sabayon linux, I didn't touch anything else and the existing remembers settings resumed working... I was inclined to agree that it was a Konsole bug when I had to switch to using the launchers to get unique NAME values instead of using the .xinitrc command lines. But now it's the konsole sessions started AFTER E17 starts that don't get the value properly assigned, while the .xinitrc command lines are resulting in unique NAME values... hunh????? What changed since March? -- | ~^~ ~^~ | <?> <?> Joe (theWordy) Philbrook | ^ J(tWdy)P | \___/ <<[email protected]>> ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
