On 12/07/2019, Ingo Schwarze <schwa...@usta.de> wrote: > Hi NilsOla, > > NilsOla Nilsson wrote on Thu, Jul 11, 2019 at 11:24:24PM +0200: > >> I am using cwm and ksh and at present my compose key >> work in st and in gvim, but not in xterm. >> I am on current updated a few weeks ago. > > Oh. Thank you for the hint. Given my clumsiness with X keyboard > configuration, i assumed it was just me, but your additional data > indicates there may actually be a regression in xterm(1). > > Who knows what a GTK leviathan like gvim is doing. But suckless > software is about the opposite of bloatware and i would be quite > surprised if it internally re-implemented the Compose mechanism. > So the fact that Compose works in the x11/st(1) port (which i > can confirm) means that i probably do have Compose correctly > configured and that xterm(1) is somehow breaking the characters > it receives from X - not all of them, but those where Compose > was involved. > > The above suspicion is supported by the fact that Compose also > works in xedit(1). It even works in xclipboard(1), xman(1), > nedit(1), except that these programs don't support UTF-8 but > appear to be hardcoded to Latin-1, such that the entered UTF-8 > characters appear as garbage two-character sequences. > > To me, this looks suspiciously like a bug now. :-(
Oh -- thank you both for that. I hadn't noticed, but that could have really bitten me, as I'm currently using xterm more, chiefly for its UTF-8 support that the console doesn't have, especially ever since I've belatedly figured out Ctrl+right-click and Ctrl+left-click in xterm. Look at all these choices I didn't know I had. :) Ian
