It would appear that on Mar 20, Carsten Haitzler did say:
> On Mon, 19 Mar 2012 14:33:04 -0400 "Joe(theWordy)Philbrook" <jtw...@ttlc.net>
> said:
>
> >
> > It would appear that on Mar 19, Carsten Haitzler did say:
> > > 3. WM_COMMAND (xprop and the command in the icccm dialog) i still don't
> > > know if it has the correct command listed (you didn't cover that).
> >
> > Opps sorry. Thing is I don't know if WH_COMMAND is supposed to include all
> > the arguments to the command or just the command itself... If the latter
> > then:
> >
> > WM_COMMAND(STRING) = { "konsole" }
> >
> > would be correct. But if it's supposed to include the entire command
> > including all command line options, then not so much...
>
> it should include the full command - arguments too. otherwise e has no ability
> to read it AND the arguments and remember to run the command PLUS arguments.
> :)
> e runs what the wm_command says to run. :) app sets this.
>
> > None of the command line option tags {IE "--name"} appear anywhere in the
> > xprop output. Though with the exception of the --profile option, the values
> > assigned to them appear scattered across:
> > "WM_CLASS(STRING)", "WM_NAME(STRING)", & "_NET_WM_NAME(UTF8_STRING)"
>
> i smell an equo upgrade breaking konsole. :)
>
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.
> > 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).
Well xterm may work better with xprop. But I have enough difficulty with
manipulating the mouse well enough to mark a selection of text, that it
matters to me that with Konsole I can then right click "c" {copy} And then use
^V to paste to *_CURSOR_* position in most gui apps {most commonly pasting a URL
into a Firefox's location field} without having to carefully position the
uncooperative mouse cursor to exactly the right spot while I emulate middle
click on my two button trackball. And/or {better yet} mark text with the
keyboard in some gui app such as LibreOffice, copy it with ^C and then I only
have to keep that durned mouse pointer anywhere within the konsole screen
While I right-click then type "p" to paste it to the cursor position of
konsole. With xterm I don't get the right click menu. And I detest the HOLD
THE BUTTON DOWN WHILE SELECTING method used by xterms <ctrl>+<LeftButton> and
<ctrl>+<RightButton> menus (for on the fly adjustments) Nor have I figured out
how to alter the color settings on the fly for those times when my tired eyes
NEED a change and I'm already many screenfuls deep into a LONG file...
I'm just glad that so far them KDE devs haven't messed up Konsole so far
that I can't use it. As while there are a few alternatives, There isn't any
such thing as a good replacement. But give them enough time, and it's bound
to happen. and then I'll likely make more use of xterm...
Be that as it may, I thank you for the help and suggestions. It has
certainly improved my understanding of how a some things work.
--
| --- ___
| <0> <-> Joe (theWordy) Philbrook
| ^ J(tWdy)P
| ~\___/~ <<jtw...@ttlc.net>>
------------------------------------------------------------------------------
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
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
