On Wed, 14 Mar 2012 18:37:04 -0400 Joe Philbrook <[email protected]> said:

> 
> Something changed:
> 
> I wasn't sure if this was an E17 issue or something specific to Sabayon
> Linux. {So far the only Distribution where I've encountered this problem}
> where the behavior changed after a recent system update.
> 
> But I've had no response to my Sabayon forum post, so I thought I'd find
> out if anybody here knows what changed...
> 
> I have a strong preference for booting to console. And then, when and if
> I'm ready for GUI, I run startx as a normal user... At which point, my
> ~/.xinitrc feeds a few applications to X that I expect to find running on
> certain specific desktop areas when E17 {Enlightenment} starts. I've used
> Enlightenment almost exclusively ever since I ran away from kde4. But one
> of the places my kde roots show is a strong preference to use Konsole as my
> "xterm" of choice.
> 
> I have two bash scripts that I expect to find running in their on Konsole
> windows with specific --profile settings. One which runs my console based
> email client {alpine} I expect to find on desktop area "1,0". The other is
> a script that runs mc via a call to "su -c" so that it sits there waiting
> on desktop area "3,2" for my root password to start the root mc session.
> 
> I also have two E17 keyboard shortcuts defined to recreate these windows on
> demand, in the event I close them or {in the case of the 2nd script} If I
> might need more than one root mc session open. 
> 
> Since Enlightenment doesn't "restore" a saved DE session like I used to do
> with kde3, I learned to use it's "Window Remembers" function to recreate the
> parts of the session I care about. And pre-Launch the ones that Enlightenment
> doesn't "Start on Login" correctly. Like for example It would start two
> Konsole sessions, But I couldn't get it to use the assorted options needed to
> load the correct executables within them, nor to use the specific konsole
> profile and {window}name definitions...

on the konsole window if u launch manually click the icon (and in the window
menu) look at window->icccm/netwm

this pops up a dialog with the window properties. specifically you want the
Command property to be the same command used to launch the app. it is up to the
app to set this correctly as the wm has no idea what the command is otherwise.
if this is set right then it should work in running with the right command +
options (the options should be there too). additionally app should set
name/class/role (or whatever is used to match the window - u can tweak what is
used) BEFORE it shows the window. title is unreliable to match here as it
changes so much, but name+class+role etc. should be reliable. if app changes
these after showing the window e will have trouble matching it up.

> Thus I use my ~/.xinitrc to initialize them with the desired options.
> 
> This has worked well for years. I use the same method on all the Linux
> distributions that I run. (I have 5 of them installed on this PC) 
> 
> Currently my ~/.xinitrc contains:
> 
> xdaliclock -12 -noseconds -builtin1 &
> konsole --workdir /home/jtwdyp/STUFF/ShuttleStuff --name F12crap --profile
> BlackYellow -e medosumc & yakuake &
> konsole --workdir ~/mail --name F2alpine  --profile BlackGray -e alpine &
> /usr/bin/enlightenment_start
> 
> 
> A key component of which is the "Unique" strings assigned to the "--name"
> flag that has for years reliably identified these two very different
> konsole instances from any other Konsole instances.
> 
> Today however, after I ran "equo upgrade" The "name" value stopped working
> properly with the ~/.xinitrc invoked instances of konsole. Sometimes they
> both wind up named "F2alpine", and sometimes they both wind up named "F12crap"

what does equo upgrade do?

> But after logging out and rerunning startx about 20 times (half of which
> were full reboots) Not once did the each wind up with their own discretely
> unique "names" within my Sabayon installation since my last:
> 
> equo update && equo upgrade
> 
> (which I do about once a month.) I note however that any instances of them
> that I fire up with the keyboard shortcuts still consistently wind up with the
> correct command defined name value. It is only the two instances that
> Enlightenment inherits from the ~/.xinitrc that this value fails to get
> correctly assigned. And It might be worth mentioning that ALL the other option
> flags do work correctly. Even the ~/.xinitrc initialized konsole instances do
> wind up with the correct working directories, as well as the correct konsole
> profiles, and with the correct executable running within them. 
> 
> Now however, in order to get E17 to place them in the correct desktop
> areas, I need to uncheck the "Window name" option in the "Remember using"
> dialog box, and rely instead on the "Title" option, and just hope that it's
> value continues to use the current format of "${A}: ${B}" where A equals
> the value assigned via the --workdir option, and B equals the value assigned
> to the -e option. (I note that A is not the same as $PWD  because "~/mail" is
> not rendered as "/home/jtwdyp/mail")

title is less reliable due to it being able to change - name/class should not.
if konsole changes name/class AFTEr showing - thats a konsole bug. if e doesnt
get the right name then its e's bug. try "xprop" and click on your console to
see all the properties after they get shown - name/class should be there eg:

WM_CLASS(STRING) = "xterm", "XTerm"

check this is correct and matches the name/class in the icccm/netwm dialog in e.

> Does anyone know what changed? Or whether this is more correctly an
> Sabayon Linux issue, or perhaps even an kde thing???
> 
> Or if you happen to know how to make sure that the window Title will always
> be rendered as "${A}: ${B}" {see above} I'd appreciate a clue.
> 
> -- 
> |  ~^~   ~^~
> |  <?>   <?>       Joe (theWordy) Philbrook
> |      ^                J(tWdy)P
> |    \___/         <<[email protected]>>
> 
> 
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing 
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> enlightenment-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/enlightenment-users
> 


-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    [email protected]


------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
enlightenment-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Reply via email to