Tridactyl: Is there a way to disable <c-w> for Firefox tab deletion and use it for word deletion, instead?

Created on 2 Apr 2019  Â·  5Comments  Â·  Source: tridactyl/tridactyl

Long term pentadactyl usage, as well as regular *nix usage has burned it into my muscles, and it is actually one of the biggest things I miss.

Most helpful comment

Another simpler, but slightly less "effective" alternative, is to mess around with ui.key.accelKey in about:config. If you change it from 17 (the default — Ctrl) to 18 (Alt) then the shortcuts for <C-w>, <C-t>, <C-n> etc. will now be <A-w>, <A-t>, <A-n>. These shortcuts will still be "reserved", but if you care more about having Ctrl keybindings free, then you're "ahead". (OTOH remapping virtually all the browser shortcuts, might mess with muscle memory.) Another alternative value for ui.key.accelKey is 91 which is the "Window key" (DOM_VK_WIN) and both "super" and "hyper" on X11. (This might collide with your WM keybindings...)

Regarding patching omni.ja, the last time that I tried, the process described in these articles worked. (Direct link to the patching script, under GPLv2.)

All 5 comments

Yes, but you have to recompile firefox with this patch. It can also be done by patching your omni.ja file but I don't have the specific steps in mind for now.

I've been toying with the idea of making omni.ja patching easy with a single command but I haven't implemented anything yet.

Another simpler, but slightly less "effective" alternative, is to mess around with ui.key.accelKey in about:config. If you change it from 17 (the default — Ctrl) to 18 (Alt) then the shortcuts for <C-w>, <C-t>, <C-n> etc. will now be <A-w>, <A-t>, <A-n>. These shortcuts will still be "reserved", but if you care more about having Ctrl keybindings free, then you're "ahead". (OTOH remapping virtually all the browser shortcuts, might mess with muscle memory.) Another alternative value for ui.key.accelKey is 91 which is the "Window key" (DOM_VK_WIN) and both "super" and "hyper" on X11. (This might collide with your WM keybindings...)

Regarding patching omni.ja, the last time that I tried, the process described in these articles worked. (Direct link to the patching script, under GPLv2.)

Related - #1590.

Another simpler, but slightly less "effective" alternative, is to mess around with ui.key.accelKey in about:config. If you change it from 17 (the default — Ctrl) to 18 (Alt) then the shortcuts for <C-w>, <C-t>, <C-n> etc. will now be <A-w>, <A-t>, <A-n>. These shortcuts will still be "reserved", but if you care more about having Ctrl keybindings free, then you're "ahead". (OTOH remapping virtually all the browser shortcuts, might mess with muscle memory.) Another alternative value for ui.key.accelKey is 91 which is the "Window key" (DOM_VK_WIN) and both "super" and "hyper" on X11. (This might collide with your WM keybindings...)

Regarding patching omni.ja, the last time that I tried, the process described in these articles worked. (Direct link to the patching script, under GPLv2.)

I was thinking to give up on Firefox because of the C-w binding, the number of times I've pressed it to delete a word and closed the tab had started giving anxiety issues. This answer should be on Firefox forum about the C-w. Thank you so much!

@aplaice Works great. I was worried that it may also remap <C-PageUp> <C-PageDn> which allow me to get away from Firefox "protected" tabs.

EDIT: Nevermind. It remaps <C-c>.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ipwnponies picture ipwnponies  Â·  4Comments

WloHu picture WloHu  Â·  4Comments

bovine3dom picture bovine3dom  Â·  5Comments

barryridge picture barryridge  Â·  5Comments

smoothchrome picture smoothchrome  Â·  4Comments