Funkcjonalność tej witryny będzie ograniczona w czasie konserwacji. Jeśli artykuł nie rozwiązuje twojego problemu i chcesz zadać pytanie, to nasza społeczność wsparcia jest dostępna na @FirefoxSupport na Twitterze i /r/firefox na Reddicie.

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

How can I change the "Go to Line" shortcut from Ctrl+J to the standard Ctrl+G?

  • 4 odpowiedzi
  • 1 osoba ma ten problem
  • 10 wyświetleń
  • Ostatnia odpowiedź od noblethought

more options

I'm used to the Ctrl+G keyboard shortcut to go to a specific line in the debugger or IDE I'm working in, across multiple IDEs. It seems very silly that even the VIM keyboard shortcut (which uses Esc, Shift + G) wouldn't give this option.

Is there ANY way, even in about:config to change this binding? I never use "Find Again" (Default for Ctrl+G) in the debugger, and it always trips me up in the middle of a flow programming state to have to shift gears to remember Ctrl + J.

Please help us non-Dvorak keyboard developers.

I'm used to the Ctrl+G keyboard shortcut to go to a specific line in the debugger or IDE I'm working in, across multiple IDEs. It seems very silly that even the VIM keyboard shortcut (which uses Esc, Shift + G) wouldn't give this option. Is there ANY way, even in about:config to change this binding? I never use "Find Again" (Default for Ctrl+G) in the debugger, and it always trips me up in the middle of a flow programming state to have to shift gears to remember Ctrl + J. Please help us non-Dvorak keyboard developers.

Wszystkie odpowiedzi (4)

more options

Unfortunately, Firefox doesn't have a keyboard shortcut remapper feature, nor are extensions able to remap built-in keys. (Yet -- hopefully someday.)

The Developer Tools team has a forum where you might be able to pick up a workaround if you don't end up getting one here (and where you might also advocate for changes):

https://discourse.mozilla.org/c/devtools


The userChrome.css file does provide for a sort of "back door" to load scripts through a feature called XBL bindings. I don't mess with such things myself, but I have an example on this page: https://www.userchrome.org/what-is-userchrome-js.html. This feature is used by the author of Classic Theme Restorer in at least one of the styling rules here: https://github.com/Aris-t2/CustomCSSforFx

more options

Note that there are a few choices for the key binding (keymap) available in the developer toolbox settings.

more options

There are, but even changing keymap layouts hasn't changed the binding for that function. There are two out of three that should, but none of them change the keymapping for that function.

more options

Jscher2000, I'll give that a shot. Thank you.