WaltS48 decreed, Read These Runes!: > On 10/26/2014 11:12 AM, RM wrote: ------------------- >> Home grown: >> >> User agent: Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/2014102213 >> Firefox/36.0 SeaMonkey/2.33a1 >> Build identifier: 20141022132455 >> >> Even the official Slackware release shows: >> >> /usr/lib64/seamonkey-2.29.1$ diff -s seamonkey seamonkey-bin >> Files seamonkey and seamonkey-bin are identical >> >> So... Who knows? >> > > > Well upon further investigation it appears my openSUSE installed version > uses seamonkey.sh to start SeaMonkey, and I have only seamonkey-bin and > seamonkey.sh.
No telling why your maintainers decided to go this way, but I'm sure there's a valid reason. > Which when I execute seamonkey.sh from a terminal gives me 29 > console.error: Failed to lookup messages, and one addons.xpi error message. > > I always use seamonkey if I manually install from the SeaMonkey Project. > Don't have any installed at this time. Historically - and in many cases, still - the .sh files were shell scripts setting environment variables for the *bin files. Apparently in SeaMonkey at least, these are now hard coded in the binaries. -- Why don't elephants eat penguins ? Because they can't get the wrappers off ... _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
