diff options
author | Runxi Yu <harriet@andrewyu.org> | 2023-08-06 11:44:33 +0800 |
---|---|---|
committer | Runxi Yu <harriet@andrewyu.org> | 2023-08-06 11:44:33 +0800 |
commit | fd85c16d29f89568ef4bf5cef3e1147e76b1a5c0 (patch) | |
tree | 9ae6f2880415a2f400ea3c6995cc597f6e4fe896 /article/sway-keysym.html | |
parent | 5eb0c6416bbc3254f886199e788f08e2008a4e20 (diff) | |
download | www-fd85c16d29f89568ef4bf5cef3e1147e76b1a5c0.tar.gz |
Unicode quotations
Diffstat (limited to 'article/sway-keysym.html')
-rw-r--r-- | article/sway-keysym.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/article/sway-keysym.html b/article/sway-keysym.html index 68a1bab..b70bdcc 100644 --- a/article/sway-keysym.html +++ b/article/sway-keysym.html @@ -35,7 +35,7 @@ xkb_symbols "basic" { // leave "basic" in-tact unless you know what you're doing key <CAPS> { [ Shift_L, Shift_L, Shift_L, Shift_L ] }; };</pre> <p> - Note that here, the ``<code>key</code>'' lines are in the form <code>key <X> { [ A, B, C, D ] } ;</code>, where ``<code>X</code>'' is the keycode symbolic name of the physical key you want to press. In my case, it is <code>CAPS</code>. Check <code>/usr/share/X11/xkb/symbols/pc</code> and <code>/usr/share/X11/xkb/symbols/latin</code>, or the relevant files for your keyboard configuration, to look up the keycode symbolic name from the name you're used to. (Looking up <code>Shift_L</code> in <code>symbols/pc</code> gets you to <code>LFSH</code>, which is what you would use in place of ``<code>X</code>''. <code>A</code> is triggered when <code>X</code> is pressed alone, <code>B</code> when it's pressd with Shift, <code>C</code> with AltGr, and <code>D</code> with both AltGr and Shift. + Note that here, the “<code>key</code>” lines are in the form <code>key <X> { [ A, B, C, D ] } ;</code>, where “<code>X</code>” is the keycode symbolic name of the physical key you want to press. In my case, it is <code>CAPS</code>. Check <code>/usr/share/X11/xkb/symbols/pc</code> and <code>/usr/share/X11/xkb/symbols/latin</code>, or the relevant files for your keyboard configuration, to look up the keycode symbolic name from the name you're used to. (Looking up <code>Shift_L</code> in <code>symbols/pc</code> gets you to <code>LFSH</code>, which is what you would use in place of “<code>X</code>”. <code>A</code> is triggered when <code>X</code> is pressed alone, <code>B</code> when it's pressd with Shift, <code>C</code> with AltGr, and <code>D</code> with both AltGr and Shift. </p> <p> <b><code>$HOME/.config/sway/config</code></b> @@ -44,7 +44,7 @@ xkb_symbols "basic" { // leave "basic" in-tact unless you know what you're doing xkb_layout "gbcustom" }</pre> <p> - Of course, replace ``<code>1:1:AT_Translated_Set_2_keyboard</code>'' with your actual keyboard identifier listed in <code>swaymsg -t get_inputs</code>. And reload Sway. + Of course, replace “<code>1:1:AT_Translated_Set_2_keyboard</code>” with your actual keyboard identifier listed in <code>swaymsg -t get_inputs</code>. And reload Sway. </p> <p> There might be better ways to do so, but I've got this to work. For these unusual setups, it is a bit complicated and not as straightforward as adding a <code>xmondmap</code> line to <code>.xinitrc</code>. Hopefully things would get better as Wayland matures. |