f10 open file menu in Fedora

[MasseGuillaume]

F10 is for step over in the debuger. But in fedora (gnome), it opens the file menu :-(. Anyone knows how to fix this ?

[lee-dohm]

Try this in your keymap.cson:

'.platform-linux':
  'f10': 'native!'

It still may not work because native! means whatever is native to Chromium, not necessarily the underlying platform. It's just that most of the time the two agree.

[batjko]

@lee-dohm Makes me wonder: Is it actually possible to control the dev tools via the key mappings, i.e. from inside Atom?
Might be interesting for some package authors to be able to enhance or otherwise access the dev tools directly.

[lee-dohm]

@batjko That's a good ❓ but not one I have the answer to. Probably worth investigating though.

[MasseGuillaume]

@lee-dohm nope does not work.

[lee-dohm]

@MasseGuillaume Well, it was worth a shot ... you could always try unset! instead of native! too.

[MasseGuillaume]

@lee-dohm dont worry ;-). I will post it here if I find a solution.

also does not work:

cat ~/.config/gtk-3.0/gtk.css 
@binding-set NoKeyboardNavigation {
unbind "F10"
}

* {
gtk-key-bindings: NoKeyboardNavigation
}

[MasseGuillaume]

no luck with unset!

[kevinsawicki]

@MasseGuillaume do you know if F10 opens file File menu in Chrome?

[MasseGuillaume]

@kevinsawicki nope

it does open file menu in other applications like terminal

[kevinsawicki]

So just to confirm, Atom on Fedora is current behaving the same as Chrome on Fedora?

[MasseGuillaume]

In chrome if I press f10 nothing happens. When I have the debugging tool it's the shortcut for step next.

In gnome terminal if I press f10 it opens up the file menu. This also happens in atom. This happens to be the default shortcut on gnome applications to open the first menu element.

[MasseGuillaume]

cat ~/.config/gtk-3.0/settings.ini
[Settings]
gtk-menu-bar-accel = ""

this solved the issues nope just the gnome-terminal

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!