Alexey I. Froloff wrote:
> On Fri, Sep 04, 2009 at 07:37:47PM +0200, Carlos R. Mafra wrote:
>> The problem with thunderbird and firefox is that their "command"
>> line in WMState are "thunderbird-bin" and "firefox-bin", instead
>> of just "thunderbird" and "firefox". So as the *-bin commands are
>> not in my $PATH, they fail to be started when wmaker starts.
> Newer FF (xulrunner) sets WM_COMMAND:
>
> $ xprop -id 0x2c00001
> ...
> WM_COMMAND(STRING) = { "xulrunner" }
>
> And /usr/bin/firefox looks like:
>
> #!/bin/sh -efu
>
> export
> MOZ_PLUGIN_PATH="/usr/lib/browser-plugins-npapi:${MOZ_PLUGIN_PATH:+":$MOZ_PLUGIN_PATH"}"
> export APP_NAME='firefox'
> export APP_PREFIX='/usr/lib/firefox'
> export XUL_APP_FILE='/usr/lib/firefox/application.ini'
>
> exec /usr/bin/xulrunner ${1:+"$@"}
>
> I wouldn't go so far to call that WM_COMMAND "wrong", it's just
> how FF itself is being executed. I guess this also applies to TB.
Ok, it may not be "wrong" per se, but it also makes wmaker
fail to restore the session correctly for me (it probably works for
you because 'xulrunner' is in your PATH).
For thunderbird 'xprop' tells me this
WM_COMMAND(STRING) = { "/usr/lib64/thunderbird-2.0.0.22/thunderbird-bin" }
whereas to start it I type "thunderbird". Yes, in the end the script will
turn out to execute the "thunderbird-bin" binary, but that is not the
command which wmaker or I used to start it (in my rootmenu EXEC has
"thunderbird")
And xjed does not set it at all, so it does not get restored even though
wmaker started it in the first place.
So I was just wondering if wmaker could have some other way of getting the
"true" command used to start the application, and not believe faithfully in the
"lies" (or imprecisions) that the applications may tell.
--
To unsubscribe, send mail to [email protected].
