Re: Using .XCompose

[Ajith R <ajithramayyan@yahoo.co.in>]

Hi Zenaan,

> Under the "Layout" tab, I have the option for "Compose key" - this is a drop down list, and I chose the "Scroll Lock" key as my compose key.


Similar options are there for KDE too. I tried setting the Compose key from the KDE settings menu after trying xmodmap -e "keysym Caps_Lock = Multi_key" suggested by Greg. My .XCompose file is:
include "%L"
<Multi_key> <s> <x>                     : "✄"   U2704 # WHITE SCISSORS

Now, things are even more strange. When I press the Caps Lock, a strange character appears. (I copy pasted it, searched the net and found it to be unicode compose character.) Then when I type s, the Caps Lock light gets switched on and the character S (caps) appears on screen. Then when I type X, the compose character and S become invisible and x/X doesn't appear. When I change focus to another window, the terminal in which I was typing shows the compose character and S.

This behaviour has not changed after I unchecked the settings through KDE settings menu, after restarting computer, re-issuing xmodmap command or changing the layout to us. The same sequence is seen with typing in Kate as well. Even when I use Scroll Lock as the compose key, the situation is only different in that the s is not capitalised.

Any idea what might be wrong?
Thanks,
ajith