profani-tty - Profanity fork with TTY improvements

	Commit message (Expand)	Author	Age	Files	Lines
*	Apply coding style	Michael Vetter	2020-07-07	1	-14/+14
*	Revert "Apply coding style"	Michael Vetter	2020-07-07	1	-15/+15
*	Apply coding style	Michael Vetter	2020-07-07	1	-15/+15
*	Add vim modeline	Michael Vetter	2019-11-13	1	-0/+1
*	Update copyright to include 2019	Michael Vetter	2019-01-22	1	-1/+1
*	Update copyright	James Booth	2018-01-21	1	-1/+1
*	Allow previous autocompletion with shift tab	James Booth	2017-04-01	1	-2/+2
*	Update Copyright	James Booth	2017-01-28	1	-1/+1
*	Allow filepath autocompletion in plugins	James Booth	2016-10-10	1	-0/+2
*	Minor code tidy cmd_ac.h	James Booth	2016-10-06	1	-6/+3
*	Make header defines consistent	James Booth	2016-07-24	1	-2/+2
*	Update GPL link in headers	James Booth	2016-07-24	1	-1/+1
*	Plugin unload remove cmd_acs and close window	James Booth	2016-07-05	1	-0/+1
*	Revert "WIP - Unload plugin commands"	James Booth	2016-06-30	1	-1/+0
*	WIP - Unload plugin commands	James Booth	2016-06-29	1	-0/+1
*	Fix command headers	James Booth	2016-05-23	1	-1/+6
*	Rename command sources	James Booth	2016-05-22	1	-0/+57

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en"> <head> <title>Sway keysym</title> <link rel="stylesheet" href="/plain.css" /> <link rel="shortcut icon" href="/favicon.ico" type="image/x-icon" /> <meta charset="utf-8" /> </head> <body> <h1>Sway keysym</h1> Article ID: 21 Under the <a href="https://swaywm.org/">Sway</a> Wayland compositor, we could set set <code>xkb_layout</code> and <code>xkb_options</code> for keyboards in order to do weird key mapping related things. Many people use <code>caps:ctrl_modifier</code> and <code>caps:escape</code> in <code>xkb_options</code> (see <a href="https://man.openbsd.org/xkeyboard-config">xkeyboard-config(7)</a> for other options) to make Caps Lock function as an extra Ctrl or Esc key. If all you want to do is do a relatively common modification like that, chances are that <code>xkb_variant</code> and <code>xkb_options</code> already has what you want, and you should just set that. <hr /> But if what you want isn't covered in the standard XKB files, hear my story. I personally wanted Caps Lock to function as an additional Shift key, which isn't covered in <code>xkb_options</code>. (<code>caps:shift</code> doesn't differ much from normal Caps Lock, make it confusingly documented and doesn't make the Caps Lock function as an extra Shift.) On X11, I would simply use <code>xmodmap -e "keysym Caps_Lock = Shift_L"</code>. Now my Caps Lock functions as an extra Left Shift. Works just alright. But now that I switched to Wayland, Sway in particular, <code>xmodmap</code> for X11 isn't going to work. What I ended up doing was the following: <code>$HOME/.xkb/symbols/gbcustom</code> <pre>default partial alphanumeric_keys xkb_symbols "basic" { // leave "basic" in-tact unless you know what you're doing include "gb" // or whatever base layout you use, most likely "us" name[Group1] = "English (UK) Customized"; key <CAPS> { [ Shift_L, Shift_L, Shift_L, Shift_L ] }; };</pre> 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. <code>$HOME/.config/sway/config</code> <pre>input "1:1:AT_Translated_Set_2_keyboard" { xkb_layout "gbcustom" }</pre> 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. 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. <a href="https://github.com/swaywm/sway/issues/4250">This GitHub issue</a> and <a href="https://www.city17.xyz/keychron/#xkb-here-be-dragons">jman's article on this</a> were extremely helpful. Thanks to <a href="https://sr.ht/~brocellous">brocellous</a> for pointing out the solution involving custom options. <hr /> Another, potentially better method involving defining custom <code>xkb_options</code>, propsed by brocellous: <code>$HOME/.xkb/symbols/customsymbol</code> <pre>// Remap caps to Shift_L partial modifier_keys xkb_symbols "caps_lshift" { replace key <CAPS> { type[group1] = "ONE_LEVEL", symbols[group1] = [ Shift_L ], actions[group1] = [ SetMods(modifiers=Shift) ] }; };</pre> <code>$HOME/.xkb/rules/evdev</code> <pre>! option = symbols custom:caps_lshift = +customsymbol(caps_lshift) ! include %S/evdev</pre> <code>$HOME/.config/sway/config</code> <pre>input "1:1:AT_Translated_Set_2_keyboard" { xkb_layout "gb" xkb_options "custom:caps_lshift" }</pre> <div id="footer"> <hr /> <a href="/">Runxi Yu's Website</a> </div> </body> </html>