What's our logging system?

AutoKey uses the standard library logging module. But I forgot that it is not that well used in AutoKey.
For the Qt GUI, you can grab a logger instance from autokey.qtui.common. I looked around and it seems that the GTK GUI does no logging at all. So you can disregard my previous comment about logging it.
Just a TODO: Add logging should be good enough. I’ll refactor the logging system used by AutoKey in the future, as that’s something on my roadmap anyways.

To track the logging, I opened #338

Can we get this in? I think catching the exception, so that it does not crash is ok for now. I can then cherry-pick it into master and wrap the lasted fixes up into 0.95.10

I'll take a look. Does the new logging system have any automated integration with the guis?

Nope. It currently works per module.

So just create a logger instance at the top (#338 (comment)), if there isn't already one and you are good to go.

Ok. Might it be worth looking at adding a handler that alerts via gui?

Definitely. In the Qt abbreviation configuration dialog, the OK button only enables, if the content is actually valid. When the content is invalid, only Cancel is available. This removed the need for an error message box that was shown there previously.

Something like disabling OK plus marking the invalid RE in red plus showing a description label should be good.

Added logger.

Also, I have a local commit that moves the contents of the 'save' functions (which are 100% shared between the two UI classes) to a separate file. I haven't pushed it to make it easier for you to merge this, but afterwards I'll need help writing the tests for them.

Merged and cherry-picked the crash mitigation into the master branch.