Closed Bug 132688 Opened 23 years ago Closed 23 years ago

consider MAILCAP and PERSONAL_MAILCAP environment variables

Categories

(Core Graveyard :: Cmd-line Features, enhancement, P1)

Sun
Solaris
enhancement

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jimmy, Assigned: bzbarsky)

References

Details

NS4 honored the MAILCAP and PERSONAL_MAILCAP environment varibles, yet Mozilla does not. I try to set MAILCAP in my wrapper script for all users to point to an appropriate mailcap file. Workaround: edit the appropriate fields in defaults/pref/unix.js . However, I believe that this has no effect once a user's profile has been created, while with the environment variables I can easily change the settings for all users at any time.
I'll take this. In NS4, does the environment variable take precendence over the preference setting?
Assignee: law → bzbarsky
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P1
Target Milestone: --- → mozilla1.1alpha
Status: NEW → ASSIGNED
Oops... I did some testing and I was wrong about NS4 honoring those environment variables. Other programs I work with honor MAILCAP (well, mutt uses MAILCAPS) and when I saw MAILCAP and PERSONAL_MAILCAP (in all upper case) in the Netscape binary I assumed it was a reference to environment variables, but in fact they are keywords in NS4's preferences file. Sorry 'bout that. It still would be nice, though.
Severity: minor → enhancement
Summary: MAILCAP and PERSONAL_MAILCAP environment variables ignored → consider MAILCAP and PERSONAL_MAILCAP environment variables
Sure. But my question remains. Do preference settings override these environment variables, or the other way around? The issue is that we want to ship with a default setup that works for most people so we ship with those preferences pre-set.... Perhaps something like the following logic?: if (prefHasUserValue()) { // user has set this in prefs.js/user.js // use that value } else if (env var set) { // use env var } else { // use default pref value from unix.js } Does that seem reasonable?
That looks right to me.
1.1alpha is frozen. Unsetting milestone and will retriage in a few days when I can make a realistic assessment of the situation.
Target Milestone: mozilla1.1alpha → ---
patch in bug 136670 fixes this.
Depends on: 136670
fixed by bug 136670 landing
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
rs vrfy.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.