A definition of a new Compose sequence should disable all existing sequences that conflict with the new one
In the Compose(5)
man page:
For example, you can include in your compose file the default Compose file by using:
include "%L"
and then rewrite only the few rules that you need to change. New compose rules can be added, and previous ones replaced.
However, <Multi_key> <C> <C> <C> <P>
has been defined in /usr/share/X11/locale/en_US.UTF-8/Compose
, and defining <Multi_key> <C> <C>
does not work because <Multi_key> <C> <C> <C> <P>
has the precedence. #63 (closed) suggests to remove this annoying sequence, but a better and more general solution would be that a definition of a new Compose sequence disable all existing sequences that conflict with the new one, as intended by the documentation.