Learn how to remap keys in CentOS 7.6. Primary goal: Swap Caps Lock and Ctrl keys. Secondary goal: Set F5 to be Escape.







- Goal
- Contents
- Brief Summary
- Project Log







After experimentation and testing, I made these final changes:
1) Set Alt_L key to perform the Control_L function. Adjust modifier map for "control" and for "alt".
2) Set Control_L key to perform the Alt_L function. Adjust modifier map for "control" and for "alt".
3) Set F5 key to perform the Escape function.
4) Set Shift + Backspace key to perform the Delete function (i.e. delete next character).
5) Automate these steps in a script. Set this script to be executed on login via the Gnome GUI.








Some reading indicates that:
- Linux uses two keyboard mappings, one for the console and one for the graphical mode (the X Window System).
- The console keyboard mapping can be altered using .
- The existing keymaps for are stored in . A description of these files is available in .
- The graphical mode keyboard mapping can be altered using or .
Source:
unix.stackexchange.com/questions/177024/remap-keyboard-on-the-linux-console
Author: michas
Date: Jan 2 '15



System details:
- Name: Shovel
- Specifications: HP 6005 Pro SFF. 3 GHz x86_64 processor (AMD II x4 B95 Quad Core), 4 GB RAM, 1 TB hard drive. Running CentOS 7.6.1810 (Core).
- More information: New computer: Shovel
- Installed items: GCC 4.8.5, Make 3.82.



Create new project directory:
remapping_keys_in_centos_76

Within new project directory, create new work directory:
work

Open a terminal and change directory to the work directory.








Key items:

and









Hm. Looks like there's a "control" modifier to which both Control_L and Control_R are mapped. Presumably, Control_L = Left Control Key and Control_R = Right Control Key.




I'll look at the man page (via running ).


Excerpts from the man page:





Notes:
- "pointer" here refers to a mouse or a similar tool.
- the xmodmap program parses all the expressions first before attempting to execute any of them.
- can put a list of xmodmap expressions into a file called .xmodmaprc and save it in the user's home directory. 1 expression per line.
- Lines that begin with an exclamation point (!) are taken as comments.
- will remove all keys that are bound to the shift lock modifier (currently, this is the Caps Lock key).
- Each physical key has a keycode (a numeric value). This keycode has an associated list of keysymbols (keysyms). Keysyms represent numeric character values. The first keysym is used when no modifier key is pressed in conjunction with this key, the second with Shift, the third when the Mode_switch key is used with this key, and the fourth when both the Mode_switch and Shift keys are used.


I'm not going to use the given example for swapping the Control and Caps Lock keys. I want to specifically set the physical keys to Control and Caps Lock, and I want to specify that this alteration will occur on login (i.e. in .xmodmaprc).



Suggestion from:
stackoverflow.com/questions/2176532/how-to-map-caps-lock-key-in-vim
Author: Dan Andreatta
Date: Feb 1 '10
- The command will map Esc to the Caps Lock key.




From earlier:
- keycode 37 is currently Control_L
- keycode 66 is currently Caps_Lock


Escape is not one of the special modifiers.






Hm. Didn't work.

Ah. I specified hex numbers, not decimal ones. The character 'v' is now a Caps Lock that won't turn back off. I'm using Right-Click + Paste instead of Control-V.


Scroll back up, find the original values for 0x37 and 0x66.




Hm. The 'f' key works fine. 'F'.
The & key works. '7'.

Caps Lock still works. Also turns off.

Control_L still works.



Run

to see the keycode-to-keysym mapping.

I note that:
- keycode 37 = Control_L NoSymbol Control_L
- keycode 55 = Caps_Lock
- keycode 66 = Caps_Lock NoSymbol Caps_Lock
- keycode 102 = Control_L NoSymbol Control_L





From earlier, these used to be:
- keycode 37 = Control_L NoSymbol Control_L
- keycode 55 = v V v V leftdoublequotemark leftsinglequotemark
- keycode 66 = Caps_Lock NoSymbol Caps_Lock
- keycode 102 = Muhenkan NoSymbol Muhenkan





Run

to see the keycode-to-keysym mapping.

I see that:
- keycode 55 = v V v V leftdoublequotemark leftsinglequotemark

Control-V now works properly again.




Run

to see the keycode-to-keysym mapping.
I see that:
- keycode 102 = Muhenkan NoSymbol Muhenkan



Future: Where do the original keysym settings come from? How might one find out all the possible keysym names?
- Ah. From the man page excerpts:




Let's try again.



Original settings:
From earlier, these used to be:
- keycode 37 = Control_L NoSymbol Control_L
- keycode 66 = Caps_Lock NoSymbol Caps_Lock




Run

to see the keycode-to-keysym mapping.
I see that:
- keycode 37 = Caps_Lock NoSymbol Caps_Lock
- keycode 66 = Control_L NoSymbol Control_L

Hm. Control_L works as a Caps Lock. Toggles on and off. But Caps Lock key does not work as Control. Let's check the modifier map.







Hm.


Result from earlier:









Let's experiment.
















Ah. Works now. So: Because I mapped the physical Caps_Lock key to the Control_L keysym, and the physical Control_L key to the Caps_Lock keysym, somehow the modifier map was altered. I then had to change the "control" modifier list by removing the Caps_Lock keysym and adding the Control_L keysym. For some reason, the physical Control_L key works fine as the Caps_Lock keysym without being present in the modifier map.







Now: I'll power cycle Shovel, and check that the original keyboard settings are restored.


Shovel turned off and on again.


Yup. Original settings for Caps Lock and Control_L have been restored.



Thoughts: When remapping keys,
- Back up any data on the computer before starting. You could make the computer unusable and have to reinstall the entire operating system.
- Archive key settings before starting.
- Plan out the changes and commands.
- Plan out the tests for success/failure before executing the changes.
- Change one key at a time, testing as you go.




I've backed up the data on Shovel.


Next: Archive current key settings. (These are the original key settings.)



From the excerpts from the man page, I know that the -pke option for the command indicates that:
"the current keymap table should be printed on the standard output in the form of expressions that can be fed back to xmodmap."

So: Using this option, I can produce an archive of the current key settings.

I should also test that restoring the archive works.







Cool.

I'll change a setting. Then I'll restore from archive.

I'll map F5 to 'a'.

In the output of I find that:
- keycode 38 = a A a A ae AE
- keycode 71 = F5 F5 F5 F5 F5 F5 XF86Switch_VT_5 F5 F5 XF86Switch_VT_5





Ok:
- F5 key now produces 'a'
- Shift + F5 now produces 'A'.
- However, Alt + F5 does not produce 'b'. I had thought the "Mode_switch key" in the man page referred to Alt.
-- It might refer to Option, but Option + F5 currently performs a splashy GUI display operation, which presumably takes precedence (assuming that Mode_switch key == Option).

In the output of I find that:
- keycode 71 = a A b B



Now, let's restore.





Computer input (keyboard, mouse) jammed for about 10-15 seconds while the command was running.



In the output of I find that:
- keycode 71 = F5 F5 F5 F5 F5 F5 XF86Switch_VT_5 F5 F5 XF86Switch_VT_5
- everything else in the output looks as expected, plus I can type these notes without any trouble.





Next: I'll try to execute a change on boot.






No .xmodmaprc file currently exists in the home directory.


Data for .xmodmaprc:







Currently, F5 produces nothing.


I'll test that running the command in the home directory sets F5 to produce 'a'.





aaa.


Yup, F5 now produces 'a'.


Next: Place the command in my user's startup script (which is run when I log in).



I know from previous experience that:
- .bash_profile
- .bashrc
are involved in the Bash shell startup process.


[some searching occurs here]


Source:
www.joshstaiger.org/archives/2005/07/bash_profile_vs.html
Author: Josh Staiger
Title: .bash_profile vs .bashrc

What is a login or non-login shell?

When you login (type username and password) via console, either sitting at the machine, or remotely via ssh:

.bash_profile

is executed to configure your shell before the initial command prompt.

But, if you've already logged into your machine and open a new terminal window (xterm) inside Gnome or KDE, then

.bashrc

is executed before the window command prompt.

.bashrc

is also run when you start a new bash instance by typing

/bin/bash

in a terminal.

Why two different files?

Say, you'd like to print some lengthy diagnostic information about your machine each time you login (load average, memory usage, current users, etc). You only want to see it on login, so you only want to place this in your

.bash_profile

. If you put it in your

.bashrc

, you'd see it every time you open a new terminal window.

Ok. I'll use .bash_profile. I only need keycodes to be set once, when I log in.

Looking in my .bash_profile, I note that it loads .bashrc as part of its operation anyway.

So: Add this line:

at the end of ~/.bash_profile.









Next: Power cycle Shovel. See if F5 has been set to produce 'a'.



Power cycle done. Log in.


Nope. F5 does not produce any character.


Hm. Open a terminal.


Still nope.






Yup. Now it does. Hm.


Ah. Evidently the GUI login on CentOS doesn't run the .bash_profile file.



On skimming through the previous article
New computer: Shovel
I find:

In the Software Selection interface, I have chosen:
- GNOME Desktop

[some searching occurs here]



Source:
access.redhat.com/discussions/1342633
Title: GNOME logins dont run .bash_profile in RHEL7
Author: Robert Krátký
Date: 6 February 2015 3:47 PM

The

~/.bash_profile

file is (should) only be sourced when Bash is started in interactive, login mode. When you're logging in graphically (using GDM or other display manager), the script that launches the session sources the

~/.profile

file.

CentOS 7 is downstream from RHEL7, so this will probably work.


Data for :



Create ~/.profile and copy this data into it.






This means that:
- .bashrc is run when each new shell is created (when you're already logged in)
- .bash_profile is the login script (run once when you log in)
- .profile is the GUI login script for GNOME (run once when you log in via the CentOS GUI).



Let's see if it works.




Power cycle done. Log in.


Nope. F5 does not produce any character.


Open a terminal.


Still nope.



Hm.



In Applications / System Tools / Settings / Details / About, I find:
- Gnome Version 3.28.2




Source:
unix.stackexchange.com/questions/172179/gnome-shell-running-shell-script-after-session-starts
edited Aug 23 '17 at 21:08
Drew Barrett
answered Dec 8 '14 at 22:23
Marcelo

You can use the program gnome-session-properties. Just execute it from your shell prompt (gnome-terminal):

$ gnome-session-properties

This will open a GUI where you can configure (i.e., add, edit, remove, enable and disable) startup programs.

Nice and easy. Enjoy.

Update: As noted by don_crissti (thanks) in the comments below, the gnome-session-properties startup programs functionality has migrated to gnome-tweak-tool since Gnome 3.12 (which btw is a great tool, but a little messier as it concentrates just too many functions). So, for versions 3.12 and above, this is the new place to look.

OBS: And btw, using this method, you don't need to create a .desktop file, you can simply specify the command line of the /home/neko/bin/auto_stuff.sh script you created (or any other script or command you want).

Run .

It opens up a GUI program called "Startup Applications Preferences". It does indeed appear to allow a user to set programs to run on startup.

Can't see invisible files (e.g. .profile) in this GUI program.


Rename .profile to GNOME_login_bash_script.sh.




Click Add:
- Name: GNOME_login_bash_script.sh
- Command: /home/spiano/GNOME_login_bash_script.sh
- Comment: Run bash script on login



Let's see if this works.




Power cycle done. Log in.


Nope. F5 does not produce any character.


Open a terminal. Still nope.



Edit GNOME_login_bash_script.sh so that it uses absolute paths.









Let's see if this works.




Power cycle done. Log in.

No. F5 does not produce any character. Open a terminal. No.





My GNOME version (3.28.2) is greater than the one mentioned in the excerpt above (3.12).

I'll try .






Hm.


On running again, and looking at the list of Startup Programs, I don't find my script listed.







Run . In the "Startup Applications Preferences" GUI program, click Add:
- Name: GNOME_login_bash_script
- Command: /home/spiano/GNOME_login_bash_script.sh
- Comment: Run bash script on login
Click Close.



Run . In the "Startup Applications Preferences" GUI program, look through the list.
- GNOME_login_bash_script is not present.



Try without underscores (the other names don't have underscores).


Run . In the "Startup Applications Preferences" GUI program, click Add:
- Name: GNOME login bash script
- Command: /home/spiano/GNOME_login_bash_script.sh
- Comment: Run bash script on login
Click Close.


Run . In the "Startup Applications Preferences" GUI program, look through the list.
- "GNOME login bash script" is not present.







Source:
ubuntuforums.org/showthread.php?t=1067101
Author: d2globalinc

HOWTO: Disable or Enable Gnome Session Startup Applications from Command Line

- As usual I am not responsible for you screwing up your install by using these instructions the wrong way! -

So I looked around, and just couldn't find out how to do this without using the GUI (Which by the way is SYSTEM->PREFERENCES->SESSIONS)

It looks like by default session startup options are located in the following directories:

/usr/share/gnome/autostart/
/usr/share/autostart/
/etc/xdg/autostart/
and then every user can have their own autostart options located in
~/.config/autostart/
(the above translates to: /home/<username>/.config/autostart/ )

So if you want to disable a startup option from command line you would just open a terminal window and remove or as I perfer - rename - the startup options corrisponding .desktop file. For example, to disable the check for new hardware on every login for every user - you could do this:

- Open a terminal window
- do the following:

Code:

sudo mv /etc/xdg/autostart/jockey-gtk.desktop /etc/xdg/autostart/jockey-gtk.orig

This will rename the jockey-gtk.desktop file (which is the New Hardware Detection Application in Ubuntu) to jockey-gtk.orig - which will disable it from starting up for all users when they login. Which was something I needed to do on a current project.

Anyway - I looked around, and I found methods for disabling startup services using the "sysv-rc-conf" package, but it was much harder to find any information about how to disable Gnome Session Startup applications without using the GUI - which was not an option for me in this case.

Hope this helps others!

Enjoy!

Shane Menshik
D2 GLOBAL INC
http://www.d2global.com

Hm.









Hm.








Let's see if this works.

Power cycle done. Log in.

Yes. F5 produces 'a'.

aaaaaaaaaaaaaaaaaaaa.


Cool.

Shift-F5?

AAAAAA.

Yup, produces 'A'.


Open a terminal. In terminal, F5 produces 'a' and Shift-F5 produces 'A'.





Run . In the "Startup Applications Preferences" GUI program, look through the list.
- "GNOME login bash script" is present.


Excellent.



Evidently the permissions for the file GNOME_login_bash_script.sh were the problem. It didn't have "execute" permission, even from its owner (spiano).


I don't know if the name of the autostart file made any difference i.e. changing it from
GNOME_login_bash_script.sh.desktop
to
GNOME_login_bash_script.desktop.









Next: Choose final key settings:
- Plan out the changes and commands.
- Plan out the tests for success/failure before executing the changes.
- Change one key at a time, testing as you go.



Changes:
1) Set Caps_Lock key to perform the Control_L function. Make appropriate adjustment to modifier map for "control".
2) Set Control_L key to perform the Caps_Lock function. Make appropriate adjustment to modifier map for "lock".
3) Set F5 key to perform the Escape function.
4) Set Shift + Backspace key to perform the Delete function (i.e. delete next character).



Tests:
1) In a text editor: Use Caps_Lock + C to copy some text. Use Caps_Lock + V to paste it.
2) In a text editor: Press Control_L. Type some text. The characters should all be upper case.
3) In : Enter Insert Mode. Press F5 key to escape Insert Mode and re-enter Command Mode.
4) In a text editor: Type some text. Position the cursor in the middle of the text. Press Shift + Backspace. The character immediately after the cursor should be deleted.



Commands:


Each physical key has a keycode (a numeric value). This keycode has an associated list of keysymbols (keysyms). Keysyms represent particular character sequences. The first keysym is used when no modifier key is pressed in conjunction with this key, the second with Shift, the third when the Mode_switch key is used with this key, and the fourth when both the Mode_switch and Shift keys are used.



I'll construct some of the necessary commands:

View modifier map:


Remove the Control_L keysym from the "control" modifier list.


Add the Control_L keysym to the "control" modifier list.


Find the keycode(s) currently assigned to the Control_L keysym.


Find the keycode(s) to which the Caps_Lock keysym is currently assigned.


Find the keycode(s) to which the F5 keysym is currently assigned.


Find the keycode(s) to which the 'a' keysym is currently assigned. Check for a space either side of the keysym character.


Find the keycode(s) to which the BackSpace keysym is currently assigned.


Note: I read through the output to find some of the keysym names e.g. "BackSpace".

Remove the Caps_Lock keysym from the "lock" modifier list.


Add the Caps_Lock keysym to the "lock" modifier list.


Find the keycode(s) to which the Delete keysym is currently assigned.


Bind a keycode to a list of keysyms.








Check current keycodes:






The F5 physical key is currently set to produce 'a'. Its keycode is 71.






Let's make the changes.


1) Set Caps_Lock key to perform the Control_L function. Make appropriate adjustment to modifier map for "control".

Remove the Caps_Lock keysym from the "lock" modifier list.






Test: 1) In a text editor: Use Caps_Lock + C to copy some text. Use Caps_Lock + V to paste it.


Didn't work.








I see that there are now two entries for Control_L in the "control" modifier list. One for each keycode, even though both keycodes have the same keysym.


Test: 1) In a text editor: Use Caps_Lock + C to copy some text. Use Caps_Lock + V to paste it.


some text. some text. some text. some text. some text. some text. some text. some text.


works. Caps_Lock key now functions as Control_L.







Next: 2) Set Control_L key to perform the Caps_Lock function. Make appropriate adjustment to modifier map for "lock".


Note: When I remove the Control binding for Control_L (and/or Caps_Lock), I can still use Control_R for Ctrl+C & Ctrl+V (copy and paste).







Tests:
1) In a text editor: Use Caps_Lock + C to copy some text. Use Caps_Lock + V to paste it.
2) In a text editor: Press Control_L. Type some text. The characters should all be upper case.



some text. some text. some text. some text. some text. some text.

Test 1 passed.

SOME TEXT. SOME TEXT. SOME TEXT.

Test 2 passed.





Next: 3) Set F5 key to perform the Escape function.

No modifiers are involved.






Test: 3) In : Enter Insert Mode. Press F5 key to escape Insert Mode and re-enter Command Mode.



Test 3 passed.






Final change: 4) Set Shift + Backspace key to perform the Delete function (i.e. delete next character).



I need to set the second keysym in the keysym list for BackSpace to be Delete.







Test: 4) In a text editor: Type some text. Position the cursor in the middle of the text. Press Shift + Backspace. The character immediately after the cursor should be deleted.



some text. some text. text. soext. me text. some text. some text. some text. some t


Works. Test 4 passed.










Ok. Success. I'll assemble the command sequence, so that it can be placed in the startup script.











Put this command sequence into .xmodmaprc.








Perform computer backup again.







Test again before rebooting.






The computer ceased to accept keyboard/mouse input for about 10-15 seconds. I could move the mouse but I couldn't click or select.







The command altered the modifier table, although not on purpose. It swapped the Caps_Lock and Control_L keycodes again but kept the same keycodes in the same positions in the modifier lists.



Compare with the output from a little earlier:







Tests:
- Caps_Lock key triggers Lock.
- F5 does not function as Escape in Vim.
- Control_L functions as a Shift key. cccCCC. But not as a Control modifier key.
- Shift + BackSpace functions as BackSpace.





Now run .





Tests:

1) In a text editor: Use Caps_Lock + C to copy some text. Use Caps_Lock + V to paste it.
2) In a text editor: Press Control_L. Type some text. The characters should all be upper case.
3) In : Enter Insert Mode. Press F5 key to escape Insert Mode and re-enter Command Mode.
4) In a text editor: Type some text. Position the cursor in the middle of the text. Press Shift + Backspace. The character immediately after the cursor should be deleted.


some text. some text. some text. some text. ASDASD ASD ASD.

In Vim, F5 functions as Escape.



some text.somse t.


Test 4 passed.





Good.



Next: Power cycle Shovel.




Shovel turned off and on again.








Tests:

1) In a text editor: Use Caps_Lock + C to copy some text. Use Caps_Lock + V to paste it.
2) In a text editor: Press Control_L. Type some text. The characters should all be upper case.
3) In : Enter Insert Mode. Press F5 key to escape Insert Mode and re-enter Command Mode.
4) In a text editor: Type some text. Position the cursor in the middle of the text. Press Shift + Backspace. The character immediately after the cursor should be deleted.



copy some text.copy some text.copy some text.copy some text.copy some text.copy some text.copy some text.

Test 1 passed.

ASD ASD ASD ASD

Test 2 passed.

Test 3 passed.

The charaediateuld be deleted.

Test 4 passed.





Excellent.








[a week or so has passed]





Swapping ctrl and caps lock has not been as good an improvement as I had hoped.

Pronation of the wrist has been reduced, true. But the control_l key (caps lock, at the moment) still has to be pressed by the little finger, which is the weakest finger and therefore the least able to handle the mechanical strain.

I have decided that the left Alt key is a better location for the control_l function. This is in the same position as the Command key on a Mac. For most Control + [other key] chord presses with the left hand, the left thumb can be used to press the Alt key, while the index finger presses the [other key]. In some cases, such as Control + C or Control + V, it is easier to use the fourth finger to press the Alt key.

Chord = pressing multiple keys at the same time with the same hand.


So, I'll change the remapping (remember that the remapping occurs on GUI login):
- Caps Lock function will go back to the Caps Lock key.
- Control_L function will move to the Alt_L key.
- Alt function will move to the Control_L key.








Next: Choose final key settings:
- Plan out the changes and commands.
- Plan out the tests for success/failure before executing the changes.
- Change one key at a time, testing as you go.



Changes:
1) Set Alt_L key to perform the Control_L function. Make appropriate adjustment to modifier map for "control" and for "alt".
2) Set Control_L key to perform the Alt_L function. Make appropriate adjustment to modifier map for "control" and for "alt".
3) Set F5 key to perform the Escape function.
4) Set Shift + Backspace key to perform the Delete function (i.e. delete next character).
5) Automate these steps in a script, which is then executed on Gnome GUI login.



Tests:
1) In a text editor: Use Alt_L + C to copy some text. Use Alt_L + V to paste it.
2) In the Gnome GUI: Press Control_L + Tab several times. This should cycle through the running applications.
3) In : Enter Insert Mode. Press F5 key to escape Insert Mode and re-enter Command Mode.
4) In a text editor: Type some text. Position the cursor in the middle of the text. Press Shift + Backspace. The character immediately after the cursor should be deleted.



Check current keycodes:





Keycodes map to these physical keys:
- 71 = F5
- 37 = Control_L
- 66 = Caps_Lock
- 22 = BackSpace
- 64 = Alt_L




Restore original settings.




Computer input (keyboard, mouse) jammed for about 90 seconds while the command was running. I was playing audio in a web browser at the same time - this might explain the increased delay.






Check current keycodes:







Restoring the setting does not restore the modifier map.


To get back to original, need to change Control_L to "control" and Caps_Lock to "lock".









Now everything's back to normal (temporarily - the modification script is still set to run on GUI login).





Let's make the changes.




1) Set Alt_L key to perform the Control_L function. Make appropriate adjustment to modifier map for "control" and for "alt".

Note: When I remove the Alt_L binding for Alt_L, I can still use Alt_R for Alt commands.










There are now two entries for Control_L in the "control" modifier list. One for each keycode, even though both keycodes have the same keysym.




Test: 1) In a text editor: Use Alt_L + C to copy some text. Use Alt_L + V to paste it.


some text. some text. some text. some text. some text. some text.

works. Alt_L key now functions as Control_L.










Next: 2) Set Control_L key to perform the Alt_L function. Make appropriate adjustment to modifier map for "control" and for "alt".


Note: "alt" in the modifier map is actually "mod1".








Hm. Two entries for Alt_L.







Test: 2) In the Gnome GUI: Press Control_L + Tab several times. This should cycle through the running applications.



Works. Control_L physical key now functions as Alt_L.




Next: 3) Set F5 key to perform the Escape function.

No modifiers are involved.






Test: 3) In : Enter Insert Mode. Press F5 key to escape Insert Mode and re-enter Command Mode.



Test 3 passed.





Next: 4) Set Shift + Backspace key to perform the Delete function (i.e. delete next character).



I need to set the second keysym in the keysym list for BackSpace to be Delete.







Test: 4) In a text editor: Type some text. Position the cursor in the middle of the text. Press Shift + Backspace. The character immediately after the cursor should be deleted.



some text. some text. somxt. some text sometme text.


Works. Test 4 passed.







Ok. Success. I'll assemble the command sequence, so that it can be placed in the startup script.











Put this command sequence into .xmodmaprc.










Perform computer backup again.







Test again before rebooting.



Restore original settings.




The computer ceased to accept keyboard/mouse input for about 30 seconds. I could move the mouse but I couldn't click or select. This time, I didn't have audio playing in a browser.




The command altered the modifier table, although not on purpose, and without any practical effect. It swapped the Alt_L and Control_L keycodes again but kept the same keycodes (rather than the keysyms) in the same positions in the modifier lists.




Compare with the output from a little earlier:






Tests:
- Control_L + Tab cycles through applications in Gnome GUI.
- F5 does not function as Escape in Vim.
- Alt_L functions as a Control key. Can copy-paste text using Alt+C, Alt+V. asd asd asd
- Shift + BackSpace functions as BackSpace.





Now run to test automation script.












Tests:
1) In a text editor: Use Alt_L + C to copy some text. Use Alt_L + V to paste it.
2) In the Gnome GUI: Press Control_L + Tab several times. This should cycle through the running applications.
3) In : Enter Insert Mode. Press F5 key to escape Insert Mode and re-enter Command Mode.
4) In a text editor: Type some text. Position the cursor in the middle of the text. Press Shift + Backspace. The character immediately after the cursor should be deleted.


some text. some text. some text. some text.
Test 1 passed.

Control_L + Tab cycles through applications in Gnome GUI.
Test 2 passed.

In Vim, F5 functions as Escape.
Test 3 passed.

some text. some me textmeext.
Test 4 passed.








Good.



Next: Power cycle Shovel.




Shovel turned off and on again.





Tests:
1) In a text editor: Use Alt_L + C to copy some text. Use Alt_L + V to paste it.
2) In the Gnome GUI: Press Control_L + Tab several times. This should cycle through the running applications.
3) In : Enter Insert Mode. Press F5 key to escape Insert Mode and re-enter Command Mode.
4) In a text editor: Type some text. Position the cursor in the middle of the text. Press Shift + Backspace. The character immediately after the cursor should be deleted.


some text. some text. some text. some text.
Test 1 passed.

Control_L + Tab cycles through applications in Gnome GUI.
Test 2 passed.

In Vim, F5 functions as Escape.
Test 3 passed.

st. some texte textxt.
Test 4 passed.






Excellent.









That's the end of this project.
















Changes from the original text:
- I have not always preserved the format of any excerpts from man pages (e.g. removing extra spaces, line-breaking newlines, word-breaking hyphens).
- I have not always preserved the format of any computer output (e.g. from running bash commands). Examples: Setting input lines in bold text, adding/removing newlines in order to make a sequence of commands easier to read, using hyphens for lists and sublists instead of indentation, breaking wide tables into consecutive sections.