1 |
Hi Simon |
2 |
|
3 |
sorry if terse translates to upset, that wasn't my intended |
4 |
tone. try confused? ...and typing at high speed. |
5 |
|
6 |
yes the workaround is effective and my gentoo / Komodo user |
7 |
is now happy. what i'm really curious about is why gentoo |
8 |
mozilla does this in the first place - other mozillas tend |
9 |
not to PERMANENTLY set this var as it has the tendency to |
10 |
interfere with other mozilla-based applications ( like |
11 |
Komodo ). |
12 |
|
13 |
thanks |
14 |
|
15 |
Jeff Griffiths |
16 |
ActiveState Technical Support |
17 |
http://www.ActiveState.com |
18 |
|
19 |
> -----Original Message----- |
20 |
> From: Simon Reynolds [mailto:sproket@××××××××.net] |
21 |
> Sent: Thursday, September 11, 2003 10:14 AM |
22 |
> To: Jeff Griffiths |
23 |
> Cc: Gentoo-Dev (E-mail) |
24 |
> Subject: Re: [gentoo-dev] MOZILLA_FIVE_HOME |
25 |
> |
26 |
> |
27 |
> On Thu, 2003-09-11 at 11:31, Jeff Griffiths wrote: |
28 |
> > why is MOZILLA_FIVE_HOME permanently set in gentoo? |
29 |
> > |
30 |
> > why on gentoo is MOZILLA_FIVE_HOME permanently set? this |
31 |
> isn't set by |
32 |
> > for example binaries from mozilla.org, which plays nice with Komodo |
33 |
> > |
34 |
> > workaround is either: |
35 |
> |
36 |
> > % unset MOZILLA_FIVE_HOME && komodo |
37 |
> Continuing in the same vein as this work-around, you could move komodo |
38 |
> off your path or rename it komodo.bin or some such and create a simple |
39 |
> sh wrapper that unsets MOZILLA_FIVE_HOME and then runs the binary. |
40 |
> |
41 |
> Considering that there are exist such simple and effective |
42 |
> work-arounds, |
43 |
> I am really surprised by the highly upset tone of your email. |
44 |
> |
45 |
> I hope this helps! |
46 |
> ~Simon Reynolds |
47 |
> |
48 |
> |
49 |
|
50 |
-- |
51 |
gentoo-dev@g.o mailing list |