From f94dfbad15f44cd49aea01202a6f8499b628dd82 Mon Sep 17 00:00:00 2001
From: Tom Willemse <tom@ryuslash.org>
Date: Tue, 13 Dec 2022 06:37:44 -0800
Subject: [PATCH] =?UTF-8?q?[Surfingkeys]=20Try=20specifying=20=E2=80=98M-<?=
 =?UTF-8?q?=E2=80=99=20and=20=E2=80=98M->=E2=80=99=20differently?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

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.
---
 surfingkeys/surfingkeys.js | 4 ++--
 1 file 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";