gmane.comp.mozilla.firefox.vimperator

Ctrl+Q keybinding and other Firefox keybindings that get activated accidentally

So after killing Firefox three times with Ctrl+Q after upgrading to
1.2 I finally checked the ChangeLog and found that Ctrl+Q has been
replaced by Ctrl+Z for that exact reason.  Ignoring the irony of it
all, isn't it time we disable all of Firefox's built in keybindings?
I wrote an add-on long ago that let you redefine Firefox's keybindings
and it must be possible to simply remove them.  Has anyone looked into
this and found that it's impossible?  Otherwise I could consider
spending an hour or two working on this.

headers

Martin Stubenschrott | 17 Aug 14:19

Re: Ctrl+Q keybinding and other Firefox keybindings that get activated accidentally

Nikolai Weibull wrote:

> So after killing Firefox three times with Ctrl+Q after upgrading to
> 1.2 I finally checked the ChangeLog and found that Ctrl+Q has been
> replaced by Ctrl+Z for that exact reason.  Ignoring the irony of it
> all, isn't it time we disable all of Firefox's built in keybindings?
> I wrote an add-on long ago that let you redefine Firefox's keybindings
> and it must be possible to simply remove them.  Has anyone looked into
> this and found that it's impossible?  Otherwise I could consider
> spending an hour or two working on this.

Well, you could just set 

	// allow key to be passed to firefox if we can't handle it
	stop = false;

to true, if you want that behavior, but I don't see the advantage. Some
(Vimperator) users still use things like F6 to focus the address bar or
F11 to switch to fullscreen, unless we have a use for those keys, i
don't see the benefit of disabling those keys.

--
Martin

headers

Doug Kearns | 17 Aug 15:46

Re: Ctrl+Q keybinding and other Firefox keybindings that get activated accidentally

On Sun, Aug 17, 2008 at 10:19 PM, Martin Stubenschrott
<stubenschrott@...> wrote:
<snip>

> Some
> (Vimperator) users still use things like F6 to focus the address bar or
> F11 to switch to fullscreen, unless we have a use for those keys, i
> don't see the benefit of disabling those keys.

Some?  Can I smell another option in the air...

Actually the one area where this really annoys me is in the command
line.

Regards,
Doug

headers

Martin Stubenschrott | 17 Aug 19:42

Re: Ctrl+Q keybinding and other Firefox keybindings that get activated accidentally

Doug Kearns wrote:

> On Sun, Aug 17, 2008 at 10:19 PM, Martin Stubenschrott
> <stubenschrott@...> wrote:
> <snip>
> 
>> Some
>> (Vimperator) users still use things like F6 to focus the address bar or
>> F11 to switch to fullscreen, unless we have a use for those keys, i
>> don't see the benefit of disabling those keys.

The problem is, not all vimperator users are so hardcore vim users as we
are. And I have seen a lot (well 2 ;)) users using ctrl-t in vimperator.
The difference is, new (non-hardcore) users will probably have more
problems to :map <C-t> <C-v><C-t> than us doing

:map <C-t> <Nop>
:imap <C-t> <Nop>
:cmap <C-t> <Nop>

Actually it would be easy to write a plugin, which disables all keys
which are not taken by vimperator. The problem is, you can never know
which other extensions the user has, and he things, vimperator does not
work with extension abc, just because it does not pass ctrl-shift-x
further.

> Some?  Can I smell another option in the air...

To be honest, I even thought about this although I am not too much of a
fan of "useless" options, but i just fear we can't find a solution which

(Continue reading)

headers

Sitaram Chamarty | 24 Aug 06:43

Re: Ctrl+Q keybinding and other Firefox keybindings that get activated accidentally

On Sun, Aug 17, 2008 at 11:12 PM, Martin Stubenschrott
<stubenschrott@...> wrote:

> The problem is, not all vimperator users are so hardcore vim users as we
> are. And I have seen a lot (well 2 ;)) users using ctrl-t in vimperator.
> The difference is, new (non-hardcore) users will probably have more
> problems to :map <C-t> <C-v><C-t> than us doing

I'm a hardcore (*) vim user, but I use Ctrl-T for a new tab, among
other things.  I often have to work on other people's browsers and IDs
and no one else I know uses vimperator, so my finger memory (aka
muscle memory) needs to have the firefox defaults for less often used
stuff.  It's OK to remember two ways of doing it for frequent actions
but not for everything, and explicitly opening a blank tab is rare
enough that I honestly want to remember only one way of doing it.

As Martin said, there's got to be ways we can protect ourselves from
certain specific keystrokes rather than the disable-all-of-them
approach.

Thanks,

Sitaram

(*) hardcore enough to use it even for COBOL programming and writing
the first version of vim's COBOL syntax file more than 10 years ago...

headers

Martin Stubenschrott | 24 Aug 11:52

Re: Ctrl+Q keybinding and other Firefox keybindings that get activated accidentally

Sitaram Chamarty wrote:
> I'm a hardcore (*) vim user, but I use Ctrl-T for a new tab, among
> other things.  I often have to work on other people's browsers and IDs
> and no one else I know uses vimperator, so my finger memory (aka
> muscle memory) needs to have the firefox defaults for less often used
> stuff.  It's OK to remember two ways of doing it for frequent actions
> but not for everything, and explicitly opening a blank tab is rare
> enough that I honestly want to remember only one way of doing it.

Actually since i started using (or well at least installing) the Fast
Dial extension, i was wondering if a :map <C-t> :tabopen<cr> would make
sense by default. This would also get rid off the beep for pressing
ctrl-t, but also be consistent with other t/T mappings. On the other
hand, the url bar wouldn't be focused then, so usage might be limited.

Opinions? Or better uses of ctrl-t for the default vimp?

--
Martin

headers

Frank Blendinger | 17 Aug 14:26

Re: Ctrl+Q keybinding and other Firefox keybindings that get activated accidentally

Hi.

Nikolai Weibull <now@...> enlightened the world by writing these
words of wisdom:
> So after killing Firefox three times with Ctrl+Q after upgrading to
> 1.2 I finally checked the ChangeLog and found that Ctrl+Q has been
> replaced by Ctrl+Z for that exact reason.  Ignoring the irony of it
> all, isn't it time we disable all of Firefox's built in keybindings?
> I wrote an add-on long ago that let you redefine Firefox's keybindings
> and it must be possible to simply remove them.  Has anyone looked into
> this and found that it's impossible?  Otherwise I could consider
> spending an hour or two working on this.

I agree very much with your idea. I would really like to have no more
Firefox keybindings - I always hit those accidentally in pass-through
mode or when some input field has focus. The ^Q to ^Z change was a
blessing, now at least I don't kill the whole browser anymore, but I
often get the print dialog in my way, as I have ^N/^P bindings to change
tabs, but they don't work all the time.

Having Firefox no more react to any keybindings at all and instead
letting Vimperator do all input handling would just be consistent. If
one wants something to be accessible fast, he can make a keybinding.
With the new :emenu that has become even simpler then before.

You would only have the Vimperator default keys plus the settings from
the vimperatorrc instead of a confusing mix of Firefox + Vimperator +
some other Plugins. Just a single place to do all the configuration.

Unfortunately I can't provide any help, I have never done any Firefox

(Continue reading)