config, doc, changelog: move selection-override-modifiers to [mouse-bindings] and validate other case

specifically, check for conflicts both when mouse bindings are set and when the selection-override-modifiers setting itself is set
This commit is contained in:
feeptr@codeberg.org 2021-11-29 22:06:35 +00:00
parent 46cadee80f
commit b52cd67467
4 changed files with 41 additions and 25 deletions

View file

@ -470,16 +470,6 @@ applications can change these at runtime.
Default: _yes_.
*selection-override-modifiers*
Modifiers. The set of modifiers which, when held, will override
attempts by programs running in the terminal to capture mouse
input.
Any modifiers in this set cannot be used for mouse bindings
themselves.
Default: Shift
# SECTION: colors
@ -875,10 +865,12 @@ of the modifiers *must* be valid XKB key names, and the button name
*must* be a valid libinput name. You can find the button names using
*libinput debug-events*.
Note that the modifiers set in *mouse.selection-override-modifiers*
(by default, *Shift*) cannot be used as modifiers in mouse bindings
since they are used to enable selection when the client application is
grabbing the mouse.
The modifiers set in *[mouse-bindings].selection-override-modifiers*
(by default, *Shift*) cannot be used as modifiers in mouse bindings,
and are instead used to enable selecting text with the mouse
irrespective of whether a client application currently has the mouse
grabbed. Because the order of bindings is significant, it's best to
set this prior to any other mouse bindings that might use *Shift*.
The trailing *COUNT* is optional and specifies the click count
required to trigger the binding. The default if *COUNT* is omitted is