Different results for changed keys order

[giallu]

Coming from Linux, I pretty much expected that pressing Compose e would yield the same as Compose e
Instead, what I get is è and ᴇ respectively.

Is this something tunable, a bug or what?

[samhocevar]

The order of keys within a sequence is important, even on Linux. For instance, on a standard Xorg installation, Compose c o will give ǒ whereas Compose o c gives ©. But it’s true that most sequences are duplicated to reduce user surprise.

What you are witnessing is an unfortunate consequence of using compose rules from Xorg and from dotXCompose; they have collisions between each other. One solution would be to remove the rules from Xcompose.txt (around line 888) but you’d have to do this after each WinCompose upgrade. Another solution would be to copy the overwritten rules from Xorg.txt to your ~/.XCompose. Neither of these are convenient, I agree. Some conflicts have already been reported to the dotXCompose project here, you may wish to report yours, too.

Plans for the future include the ability to disable sequences individually (see bug #24) and add custom ones from the GUI (#25).

[samhocevar]

You can now (as of 0.8.1) disable all the rules from dotXCompose, or as explained above, re-add your own custom rules that will override the ones from dotXCompose.

I believe that these workarounds are enough to close this bug. But I still plan to add more fine-grained control over this in the future, where single rules can be disabled or their priority changed.