Hi, On Sat, Apr 16, 2005 at 12:50:02PM +0900, Choe Hwanjin wrote: > XMODIFIERS environment variable is for XIM client not the server.
I totally agree on this. > If XMODIFIERS variable is set before running scim or other XIM server, > it may make a problem. So XIM should unset the XMODIFIERS env. > variable. Hmmm... I was afraid of this kind of comments. > Let's think an example. Sure. > Some xim runs on XMODIFIERS variable which is for itself. May some > code of the xim has text entry and the text entry widget may try to > connect to the xim server according to the XMODIFIRES. OK. scim certainly has a case of opening panel application for the configulation. I was kind of afraid this situation thus asking this in scim ML. > So it try to connect itself. This make some problem. My > implementation(http://nabi.kldp.net/) set the XMODIFIERS variable to > none before IMOpenIM. I initially did not under stand your web site until I clicked "English" :-) I am convinced that you are a good authority on this topic. > XIM server program already may have the solution > for this kind of problem :) > But I think the safer way to launch scim is: > unset XMODIFIERS > scim -d Sure. I think question is "What is the safer way?" I agree with your assessment here. > And for client we need XMODIFIERS variable: > XMODIFIERS="@im=SCIM" > anyclient & Since my X startup and IM start up configuration utility does not start "anyclient", I will do: unset XMODIFIERS scim -d XMODIFIERS="@im=SCIM" in the script and let the Debian menu to start "anyclient". I will do this in my next upload of Debian package m17n-env which set up scim under X for Debian. Osamu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
