Currently, my input method defined in ~/.xinputrc is xim. The files reads:
run_im xim
This allows me to keep a custom mapping of Compose sequences in ~/.XCompose. It works everywhere inside the graphical environment, except in the Unity dash/Launcher, where keyboard sequences behave like in a standard installation (i.e., without defining xim as input method).
# EXPECTED BEHAVIOR
I should be able to use my compose sequences defined in ~/.XCompose . For example, one of the sequences is:
<dead_acute> <c> : "ç" ccedilla # LATIN SMALL LETTER C WITH CEDILLA
However, in the dash I get a ć (c-acute). See screenshot provided.
# CURRENT BEHAVIOR
None of my compose sequences in ~/.XCompose work. This problem happens 100% of the time.
# PROBLEM DESCRIPTION
Input method does not work in the Unity Dash.
Currently, my input method defined in ~/.xinputrc is xim. The files reads:
run_im xim
This allows me to keep a custom mapping of Compose sequences in ~/.XCompose. It works everywhere inside the graphical environment, except in the Unity dash/Launcher, where keyboard sequences behave like in a standard installation (i.e., without defining xim as input method).
# EXPECTED BEHAVIOR
I should be able to use my compose sequences defined in ~/.XCompose . For example, one of the sequences is:
<dead_acute> <c> : "ç" ccedilla # LATIN SMALL LETTER C WITH CEDILLA
However, in the dash I get a ć (c-acute). See screenshot provided.
# CURRENT BEHAVIOR
None of my compose sequences in ~/.XCompose work. This problem happens 100% of the time.