aboutsummaryrefslogtreecommitdiffstats
path: root/surfingkeys/surfingkeys.js
diff options
context:
space:
mode:
authorGravatar Tom Willemse2022-12-13 06:37:44 -0800
committerGravatar Tom Willemse2022-12-13 06:37:44 -0800
commitf94dfbad15f44cd49aea01202a6f8499b628dd82 (patch)
treee14d65b424089bae64411bbac66176e0063f726d /surfingkeys/surfingkeys.js
parent6474e5b0b2095e6dfb072577ca60a14524e31ee4 (diff)
downloadnew-dotfiles-f94dfbad15f44cd49aea01202a6f8499b628dd82.tar.gz
new-dotfiles-f94dfbad15f44cd49aea01202a6f8499b628dd82.zip
[Surfingkeys] Try specifying ‘M-<’ and ‘M->’ differently
The keybindings show up properly in the keybinding list, but they don't work. I'm wondering if this particular change is going to cause a syntax error, or perhaps Surfingkeys can figure out that those ‘<’ and ‘>’ are part of the keybinding.
Diffstat (limited to 'surfingkeys/surfingkeys.js')
-rw-r--r--surfingkeys/surfingkeys.js4
1 files changed, 2 insertions, 2 deletions
diff --git a/surfingkeys/surfingkeys.js b/surfingkeys/surfingkeys.js
index 3d0dd68..bebee27 100644
--- a/surfingkeys/surfingkeys.js
+++ b/surfingkeys/surfingkeys.js
@@ -16,8 +16,8 @@ api.map('<Alt-n>', 'R');
api.map('<Ctrl-v>', 'P');
api.map('<Alt-v>', 'U');
-api.map('<Alt-Shift-.>', 'G');
-api.map('<Alt-Shift-,>', 'gg');
+api.map('<Alt->>', 'G');
+api.map('<Alt-<>', 'gg');
api.Hints.setCharacters('arstdhneio');
api.hintAlign = "left";