|
|
35.
|
|
|
Switch to workspace on the left
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
data/50-mutter-navigation.xml:131
|
|
|
36.
|
|
|
Switch to workspace on the right
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
data/50-mutter-navigation.xml:134
|
|
|
37.
|
|
|
Switch to workspace above
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
data/50-mutter-navigation.xml:138
|
|
|
38.
|
|
|
Switch to workspace below
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
data/50-mutter-navigation.xml:142
|
|
|
79.
|
|
|
To enable experimental features, add the feature keyword to the list. Whether the feature requires restarting the compositor depends on the given feature. Any experimental feature is not required to still be available, or configurable. Don’t expect adding anything in this setting to be future proof. Currently possible keywords: • “scale-monitor-framebuffer” — makes mutter default to layout logical monitors in a logical pixel coordinate space, while scaling monitor framebuffers instead of window content, to manage HiDPI monitors. Does not require a restart. • “kms-modifiers” — makes mutter always allocate scanout buffers with explicit modifiers, if supported by the driver. Requires a restart. • “rt-scheduler” — makes mutter request a low priority real-time scheduling. Requires a restart. • “autoclose-xwayland” — automatically terminates Xwayland if all relevant X11 clients are gone. Requires a restart. • “x11-randr-fractional-scaling” — enable fractional scaling under X11 using xrandr scaling. It might reduce performances. Does not require a restart.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
data/org.gnome.mutter.gschema.xml.in:116
|
|
|
82.
|
|
|
Timeout for check-alive ping
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
data/org.gnome.mutter.gschema.xml.in:161
|
|
|
83.
|
|
|
Number of milliseconds a client has to respond to a ping request in order to not be detected as frozen. Using 0 will disable the alive check completely.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
data/org.gnome.mutter.gschema.xml.in:162
|
|
|
86.
|
|
|
Cancel any active input capture session
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
data/org.gnome.mutter.gschema.xml.in:187
|
|
|
100.
|
|
|
Allow X11 grabs to lock keyboard focus with Xwayland
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
data/org.gnome.mutter.wayland.gschema.xml.in:70
|
|
|
101.
|
|
|
Allow all keyboard events to be routed to X11 “override redirect” windows with a grab when running in Xwayland. This option is to support X11 clients which map an “override redirect” window (which do not receive keyboard focus) and issue a keyboard grab to force all keyboard events to that window. This option is seldom used and has no effect on regular X11 windows which can receive keyboard focus under normal circumstances. For a X11 grab to be taken into account under Wayland, the client must also either send a specific X11 ClientMessage to the root window or be among the applications allowed in key “xwayland-grab-access-rules”.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
data/org.gnome.mutter.wayland.gschema.xml.in:71
|
