On 2019-10-24 07:50, Steve Langasek wrote: > On Thu, Oct 24, 2019 at 12:06:38AM -0000, Gunnar Hjalmarsson wrote: >> wondering if that line shouldn't rather read something like this: >> >> <Multi_key> <backslash> <parenright> : "☭" # HAMMER AND SICKLE >> >> (which works with IBus provided that there is a defined compose key) > > Sure, this is a valid alternative, and just replacing the <\> with > <backslash> is enough to unbreak my Delete key. (I don't care about > whether it causes the compose sequence to work,
Please.. Whether it works in some case is reasonably relevant. If I open gedit from terminal, I get these complaints: (org.gnome.gedit:3821): Gtk-WARNING **: 14:11:14.241: Could not get code point of keysym \ (org.gnome.gedit:3821): Gtk-WARNING **: 14:11:14.242: Could not get code point of keysym ) (org.gnome.gedit:3821): Gtk-WARNING **: 14:11:14.242: compose file /home/gunnar/.XCompose does not include any keys besides keys in en-us compose file So Gtk does not understand it, and - needless to say - it doesn't work. If I replace <\> with <backslash> and <)> with <parenright>, Gtk stops complaining and it works, kind of. I.e. pressing \ followed by ) gives me ☭. But then I can't use my \ key for anything else, so this kind of composing is pretty useless without including <Multi_key> too. My observations are true both with and without IBus. IBus provides the extra 'feature' with involving the Delete key, though. > IBus does not define the syntax of .XCompose, Right. Probably Gtk or libx11 does. > It is not for ibus to retroactively declare the file to be > "syntactically incorrect"; I suppose you don't know if it worked in 19.04. I guess it did not, and then the file has been incorrect for a long time. > and regardless, if it has decided that the file is syntactically > incorrect, this should not result in changes to the behavior of an > unrelated key. Ok.. Do you plan to submit an upstream issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1849399 Title: ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete key Status in ibus package in Ubuntu: Triaged Bug description: After upgrade to 19.10, I found that my Delete key was not working as a Delete key, but that instead if I hit Delete twice it would print the character ☭. Since others were not reporting this issue, I had a look around at my input config and remembered that I had ibus configured from a long time ago in order to support Chinese input. If I disable ibus (either by unsetting the environment variables; or by killing ibus-daemon), then the Delete key works again as expected. This is a regression in behavior since Ubuntu 19.04, where I had the same input setup on my desktop but the Delete key worked without problems. I'm also not sure how to disable ibus, now that I am in this situation; or if ibus is expected to always be running. The problem persists if I run ibus-setup and remove Chinese SunPinyin from the list of input methods, leaving only "English - English (US)". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1849399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
