gnome-shell itself now handles the screencast key too.

gnome-shell itself now handles the screenshot keys. This is required to
easily provide same-frame response to pressing a screenshot key.

This creates new "X-static" binding entries in the configuration store
which store all the previously hard-coded keys. The effect is that it is
possible for users to override the behaviour, with the caveat that newly
added keybindings will not be picked up for that key.

The key name is a translated string to describe the keybinding. However,
it was never used, so drop it.

Jian-Hong Pan authored Mar 28, 2019 and Benjamin Berg committed Mar 28, 2019

The Acer Veriton Z4660G/Z4860G/Z6860G series AIO desktops have a
brightness button in the bottom.  The KEY_BRIGHTNESS_CYCLE event will be
sent from ACPI video module in kernel when the button is pressed.

This commit adds the binding for the KEY_BRIGHTNESS_CYCLE event sent
from the button as a media-key.

#117

Andrea Azzarone authored Jul 18, 2018 and Jonas Ådahl committed Feb 20, 2019

Use META_KEY_BINDING_IGNORE_AUTOREPEAT flag for all the toggle shortcuts and for
all the shortcuts where a repeated key-press could cause weird or useless
behaviour.

Fixes: #68

Andrea Azzarone authored Jul 18, 2018 and Jonas Ådahl committed Feb 20, 2019

Support the grabFlags parameter of the GrabAccelerator and
GrabAccelerators methods of the DBUS org.gnome.Shell API. For the moment
always use META_KEY_BINDING_NONE.

Some bluetooth keyboards have only 5 rows of keys, so the top row has the:
1-9, 0, -, + keys. These not only double as function keys using Fn + key,
but also as media-keys, e.g. next/prev song, using Ctrl + Fn + key.

Unfortunately the firmware for these keyboards is somewhat buggy and when
sending media keys they send along the Ctrl modifier, so we receive e.g.
"Ctrl + next-song" this commit adds bindings for Ctrl + media-key for the
media-keycodes send by these keyboards, so that these work as expected.

Hans de Goede authored Feb 19, 2018 and Benjamin Berg committed Mar 16, 2018

Some budget laptops send Ctrl + Super + custom-scancode when their
touchpad-toggle hotkey (Fn + something) gets pressed.

hwdb will map the custom-scancode to TouchpadToggle, but we need to deal
with the Ctrl + Super in the media-keys plugin, add a mapping for this.

https://bugzilla.gnome.org/show_bug.cgi?id=793610

Allow users to configure the microphone mute key. Many laptops do not
have a microphone mute key, so it can make sense for users to map it to
another key (e.g. Shift+Mute).

https://bugzilla.gnome.org/show_bug.cgi?id=793596

The current situation is that udev maps the microphone key to F20, which
is then mapped to XF86AudioMicMute by the X keyboard config. The
requirement to explicitly handle F20 is therefore gone since the
xkeyboard-config change has been merged mid 2013.

See also https://bugs.freedesktop.org/show_bug.cgi?id=54171

https://bugzilla.gnome.org/show_bug.cgi?id=793596

These are the sole remaining users of the xrandr plugin DBus API which
we want to remove in order to move the functionality to mutter. The
key binding handling will be moved to mutter as well.

https://bugzilla.gnome.org/show_bug.cgi?id=782231

Bastien Nocera authored Jun 25, 2017 and Rui Matos committed Jul 14, 2017

3 precise presses = 1 non-precise press

https://bugzilla.gnome.org/show_bug.cgi?id=650371

Hans de Goede authored May 10, 2017 and Bastien Nocera committed May 15, 2017

...and map it to RFKILL_KEY.

This depends on a X-server + libX11 or libxkbcommon which actually support
the XF86RFKill keysym and a xkeyboard-config which contains a binding for
it. Specifically the following changes are needed:
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf
https://github.com/xkbcommon/libxkbcommon/commit/939d0909a427bdb076dfbba4ccce440391c6b308
https://patchwork.freedesktop.org/patch/156341/

See https://bugzilla.gnome.org/show_bug.cgi?id=760517

https://bugzilla.gnome.org/show_bug.cgi?id=781505

This is what Windows hardcodes, and some laptops (such as the HP Stream
11") have keyboards with "help" physical keys that send Super+F1 when
pressed.

https://bugzilla.gnome.org/show_bug.cgi?id=764220

Add support for the XF86Bluetooth, XF86WLAN and XF86UWB media keys.
The first one will toggle Bluetooth on/off, as the Bluetooth panel does,
the latter ones will toggle the global software killswitch.

The reasoning behind those 2 keys toggling the global software
killswitch is that:
- we don't have a killswitch for only WiFi
- there are very very few laptops with a UWB killswitch button, if
  anyone actually remembers what UWB actually is
- there are no XF86 keys for the global killswitch, so they usually get
  mislabeled as the WLAN killswitch

https://bugzilla.gnome.org/show_bug.cgi?id=661643

gnome-shell does not allow to grab any particular key combo more
than once, even when the corresponding keybinding modes don't
overlap, so the FOO_KEY_NO_DIALOG shortcuts introduced in commit
b7827c13 never actually worked.
Instead, use the new 'action-mode' parameter that was added to the
'Activated' signal to determine whether to a power action should
be interactive or not.

https://bugzilla.gnome.org/show_bug.cgi?id=741762

The type was renamed in gnome-shell to account for usage besides
keybindings (namely gestures), so do the same here to keep the
headers in sync.

Allowing random people to create files in the user's home folder
while the screen is locked is unexpected at best, so block the
corresponding shortcuts (while still allowing taking screenshots
to the clipboard for bug reports/reviews etc.).
While at it, adjust the shortcut for screencasts as well (though
the change their is purely informational, as screencasts are already
blocked by the shell while locked).

https://bugzilla.gnome.org/show_bug.cgi?id=737456

This is bound by default to XF86Tools

This allows us to not include shortcuts-list.h in other files and thus
avoids the media_keys array being defined in more than one place.

https://bugzilla.gnome.org/show_bug.cgi?id=730765

We allow using the power key pretty much everywhere now, but
we also ensure that we never show interactive dialogues on the
lock screen (something that was possible with other suspend/power
buttons already if more than more than one user was logged in,
or an interactive shutdown was configured).

See https://bugzilla.redhat.com/show_bug.cgi?id=980692

https://bugzilla.gnome.org/show_bug.cgi?id=707095

https://bugzilla.gnome.org/show_bug.cgi?id=704435

As recently added in:
https://bugs.freedesktop.org/show_bug.cgi?id=54171

Windows+O is used on recent Windows 8 certified hardware for the
orientation lock.

https://bugzilla.gnome.org/show_bug.cgi?id=697190

https://bugzilla.gnome.org/show_bug.cgi?id=694986

Not every keybinding is useful at any moment, for instance it does
not make sense to launch the calculator from the lock screen. The
shell API allows to enable keybindings selectively, make use of that
by passing appropriate mode flags for each keybinding.

https://bugzilla.gnome.org/show_bug.cgi?id=693016

As per the comment in commit 5cda26ee, use F20, not F2 as the temporary
key until it can be captured in X.

https://bugzilla.gnome.org/show_bug.cgi?id=692071

Even though it can't be captured in X yet, we use F20 for that
key in the meanwhile.

https://bugzilla.gnome.org/show_bug.cgi?id=651051

For conflict resolution in the shortcuts section of the Keyboard panel.

https://bugzilla.gnome.org/show_bug.cgi?id=691629

These are now provided by gnome-shell.

This reverts commit fc58c347.

https://bugzilla.gnome.org/show_bug.cgi?id=690106

Rui Matos authored May 29, 2012 and Bastien Nocera committed Jun 01, 2012

https://bugzilla.gnome.org/show_bug.cgi?id=676102

Add a keyboard shortcut for taking a screenshot of an area, and other
three items for clipboard actions.

https://bugzilla.gnome.org/show_bug.cgi?id=652489

The shortcuts for launching a terminal and taking screenshots have
been provided by the wm historically, but it makes more sense to
handle them like other global shortcuts in the media-keys plugin.

https://bugzilla.gnome.org/show_bug.cgi?id=663623

By not keying the shortcut type enum to the number of shortcuts
that we hard-code. Also refactor a few functions to reduce duplication.