Re: Mozilla on win2k :-(

[Mario Vukelic <mario.vukelic@chello.at>]

On 07 Aug 2001 20:49:37 +0100, P Kirk wrote:
> >http://www.mozilla.org/unix/customizing.html#keys
> >-- 
> Way way to technical for me.  But thanks for the link.

As promised, my stab at your problem: As you noted on the list, the link
seems to point to UNIX configurations, but I guess that it works for
win, too. However, I've never seen a win mozilla, so I'm not shure. I'll
try to explain how to do it, anyway.

I think your problem is strange, since according to the given document
"Accel is the primary modifier key on the current platform. By default,
it's tied to control on Windows and Unix, command on Mac, but it's
configurable". So, on win, it should be Ctrl anyway.

You can try that:
Acoording to http://www.mozilla.org/unix/customizing.html#prefs :
"Normal prefs are kept in prefs.js in the user's profile directory
(which is overwritten by Mozilla every time a pref is changed) [MV: that
means "changed in the Preferences dialog"], but here's a tip: prefs or
other JavaScript that you don't want overwritten (e.g. comments) can be
put in a file called user.js in the same directory, which is under the
user's control and is read but never written by Mozilla."

So, in your user's config directory (where the file bookmarks.html
lives) you have a file prefs.js. Search for it. On my debian machine
it's in /home/mario/.mozilla/default/wom5kwuo.slt/prefs.js
("wom5kwuo.slt" is a directory mozilla creates automatically on first
installation, its name varies).
When you've found prefs.js, create a text file user.js in the same
directory. Put this in there ("//" marks a comment):


//
// Personal prefs which mozilla shouldn't overwrite.
// The key codes are given in
// http://www.mozilla.org/unix/customizing.html#accel
//
// Windows-style access keys:
user_pref("ui.key.accelKey", 17);
user_pref("ui.key.menuAccessKey", 18);
user_pref("ui.key.menuAccessKeyFocuses", true);


Save and Exit. Now restart mozilla. Does it work?
Attention:
"One caution with using user.js: prefs set to non-default values in
user.js are also written to prefs.js, so removing or commenting out pref
settings in user.js doesn't necessarily cause Mozilla to stop using your
previous pref setting. If you change user.js and aren't getting the
results you expect, be sure to check prefs.js to make sure it isn't
setting a conflicting value."

Good luck and please mail me if it works and if not.
Kind regards, M.

-- 

I did not vote for the Austrian government