kpsh 2.2.0

I’ve released kpsh 2.2.0. There’s one bug which I’m aware of, but I don’t know how to fix it and I doubt I’ll ever do so. It’s related to wtype backend which kpsh may use to autotype passwords. Sometimes when auto typing ends, the next pressed key has a key value 0, often followed by the actual key, and is recognized as a NoSymbol. Some menus close upon receiving such key I suspect that this is an error wlroots’ implementation of virtual keyboard protocol.

The workaround is to either live with it (kpsh-menu merely goes back to the password list) or switch backend to ydotool (but ydotool doesn’t support Unicode characters).