SCIM and why it may not be a good idea

[gingrich]

Maybe I'm just being curmudgeonly, but I am less than impressed with the "improvement" of adding SCIM to KDE. I've poked around and don't see an obvious way to remove/turn it off. The real issue is the truly evil things that start to happen when SCIM interacts with text mode windows and vim in those windows.

I've repeatedly tried looking through the configuration dialogs and in the files in /etc, A quick search revealed:

/etc> find . -type f -print | xargs grep scim | wc -l
134


So, if I want to manually remove it, I'll need to change at least 134 lines in a variety of configuration files.

Just a quiet plea from someone who's been using Unix/Linux for a while — one of the earliest philosophical standards for the design of Unix was the principle of "least surprise" — I submit that a spell checker that tries to grab command mode codes in vim is being very surprising indeed. (And probably deserves to be shot If you're going to design stuff that works like this, please leave me an easy to find escape.

Resuming normal lurking.....

> please leave me an easy to find escape.

perhaps you will be forced (with many others) to escape KDE and leave
it to the bubblegum crowd who seem to forever chase glitz on the
bloody edge...

and, do your coding in (say) vim running in a Xfce spawned x-terminal..

--
brassy

[KJ44]

I once encountered SCIM on a SLES machine, it's so annoying!

Why not remove SCIM using the YaST software management?