aboutsummaryrefslogtreecommitdiff
path: root/sway/commands
diff options
context:
space:
mode:
authorBrian Ashworth <bosrsf04@gmail.com>2019-12-15 01:33:33 -0500
committerDrew DeVault <sir@cmpwn.com>2019-12-16 12:03:11 -0500
commit452a615bb8f546fbeaddd7bacc71b5c597ab5629 (patch)
treea8a2b726fd510e906f7c27eb8510eae2bdd986b3 /sway/commands
parent2b51c5b2942fbedfe34a912b47616e98cfcea02e (diff)
seat_cmd_keyboard_grouping: change keymap to smart
This removes `seat <seat> keyboard_grouping keymap` and replaces it with `seat <seat> keyboard_grouping smart`. The smart keyboard grouping will group based on both the keymap and repeat info. The reasoning for this is that deciding what the repeat info should be for a group is either arbitrary or non-deterministic when multiple keyboards in the group have repeat info configured (unless somehow exposed to the user in a reproducible uniquely identifiable fashion).
Diffstat (limited to 'sway/commands')
-rw-r--r--sway/commands/seat/keyboard_grouping.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/sway/commands/seat/keyboard_grouping.c b/sway/commands/seat/keyboard_grouping.c
index 959c6f94..5ad0f408 100644
--- a/sway/commands/seat/keyboard_grouping.c
+++ b/sway/commands/seat/keyboard_grouping.c
@@ -15,11 +15,11 @@ struct cmd_results *seat_cmd_keyboard_grouping(int argc, char **argv) {
struct seat_config *seat_config = config->handler_context.seat_config;
if (strcmp(argv[0], "none") == 0) {
seat_config->keyboard_grouping = KEYBOARD_GROUP_NONE;
- } else if (strcmp(argv[0], "keymap") == 0) {
- seat_config->keyboard_grouping = KEYBOARD_GROUP_KEYMAP;
+ } else if (strcmp(argv[0], "smart") == 0) {
+ seat_config->keyboard_grouping = KEYBOARD_GROUP_SMART;
} else {
return cmd_results_new(CMD_INVALID,
- "Expected syntax `keyboard_grouping none|keymap`");
+ "Expected syntax `keyboard_grouping none|smart`");
}
return cmd_results_new(CMD_SUCCESS, NULL);