ir-keytable -c -w /etc/rc_keymaps/file

having got ir-keytable the way I want it and all key codes working with vlc and liblic-client0 removed, I then reinstalled vlc and all the key codes still worked, even after a reboot. So now I'm guessing that liblirc-client0 prevents proper setup of the key codes if it is installed, but after it's already been setup, it has no effect on them. Maybe someone else can figure out what is going on.

OK, I changed one key code and then issued this command;
root@mythfe0:/home/wes# ir-keytable -c -w /etc/rc_keymaps/myremotes
Then tested that it worked like this]
root@mythfe0:/home/wes# ir-keytable -t
Testing events. Please, press CTRL-C to abort.
555.460958: event type EV_MSC(0x04): scancode = 0x28
555.460958: event type EV_KEY(0x01) key_down: KEY_SEMICOLON(0x0027)
555.460958: event type EV_SYN(0x00).
;555.566930: event type EV_MSC(0x04): scancode = 0x28
555.566930: event type EV_SYN(0x00).
555.836028: event type EV_KEY(0x01) key_up: KEY_SEMICOLON(0x0027)
555.836028: event type EV_SYN(0x00).
Then tried it in notes clipboard and it didn't work.
Then rebooted and it worked. So I guess it takes a reboot, meaning the ir-keytable -c -w /etc/rc_keymaps/myremotes command doesn't fully support all changes that need to happen for the rc keymap file to work right in other apps. BTW, this was all with vlc installed along with liblirc-client0. With them removed, the changes worked without a reboot iirc. Might want to close this out. I don't know.

To further investigate this issues, a question is if the main lirc package is installed. If so, the lircd.socket, lircd.service and lircd-uinput.services should be disabled and stopped. If problem persists, with or without liblircclient installed, this should be re-assigned to the kernel

Late comment: vlc does not depend on lirc any more, so this should not happen to new installations.

Work around for existing installations is to either remove the lirc package or simply disable lircd.socket, lircd.service and lircd-uinput using systemctl.