Talk:Keyconfig extension: Difference between revisions

From MozillaZine Knowledge Base
Jump to navigationJump to search
(a few comments)
No edit summary
Line 1: Line 1:
Changed the issues mentioned by you.
--[[Christian Bischoff]] 28.01.2005 23:24
<blockquote>''Shortcuts defined via a key can be changed but only changing those which itself call a function (those with a command or oncommand attribute) has an effect (all others fulfill only cosmetic purposes it seems and are grayed out).''</blockquote>
<blockquote>''Shortcuts defined via a key can be changed but only changing those which itself call a function (those with a command or oncommand attribute) has an effect (all others fulfill only cosmetic purposes it seems and are grayed out).''</blockquote>
This will make no sense for those who are not familiar with XUL. It doesn't make much sense to me either (I know XUL but not that familiar with keyconfig - therefore I'm not sure how should it be changed).  
This will make no sense for those who are not familiar with XUL. It doesn't make much sense to me either (I know XUL but not that familiar with keyconfig - therefore I'm not sure how should it be changed).  

Revision as of 22:24, 28 January 2005

Changed the issues mentioned by you. --Christian Bischoff 28.01.2005 23:24


Shortcuts defined via a key can be changed but only changing those which itself call a function (those with a command or oncommand attribute) has an effect (all others fulfill only cosmetic purposes it seems and are grayed out).

This will make no sense for those who are not familiar with XUL. It doesn't make much sense to me either (I know XUL but not that familiar with keyconfig - therefore I'm not sure how should it be changed).

You can add the following lines to the file prefs.js in your profile to get the described results. All instances of Firefox/Thunderbird must be closed before editing this file. After editing start FF/TB and open the Keyconfig window to add your keyboard shortcut.

The part about "the following lines" should probably be changed too.

You could also add the lines to your user.js, but after starting FF/TB you have to delete the lines from the user.js. If you won't delete them, they will be applied again with the next start of FF/TB and will overwrite (delete) the assigned keyboard shortcuts.

If you have to delete the lines from user.js, there's no point in adding them there in the first place, so that paragraph should be removed. --Asqueella 12:32, 26 Jan 2005 (PST)


why did you remove the contents of the article? did you? --Asqueella 07:11, 18 Jan 2005 (PST)

nevermind. Redirected both pages, Firefox : Tips : Change and add keyboard shortcuts with Keyconfig and Firefox : FAQs : Change Keybindings to Keyconfig extension. Makes more sense to me since the tip is not Firefox-only. --Asqueella 07:22, 18 Jan 2005 (PST)

I removed it. I was a bit confused, because I am new in Wiki. ;) I would like to delete this page: http://kb.mozillazine.org/Firefox_:_Tips_:_Change_and_add_keyboard_shortcuts_with_Keyconfig No links points to it any more.

Isn't it possible to get the "pre box" around the whole text? Like it is, it looks strange.

I will make one Keyconfig Page for Firefox and one for Thunderbird. But I will do that tomorrow or so and will also add many more prefs.

--Christian Bischoff 19.01.2005 01:37


Moved Menu editor talk to my user talk page.
The page was redirected (anybody can redirect a page, only chosen can delete pages).
Are the pages for Fx/TB are going to be actually different, or only the examples section? If the latter, you could create a few sections with examples for different applications. If the "all-in-one" page is going to be too cluttered, I suggest creating pages like "Using keyconfig in Firefox" etc.
The pre'ed text, I know it looks weird, but the original variant looked like junk. I was thinking about adding "linefeed" symbols when the line is too long, but I don't have much time now. --Asqueella 01:44, 19 Jan 2005 (PST)