On Mon, Oct 24, 2005 at 12:14:16PM +0800, Emfox Zhou wrote:
> im-switch is enabled once it is installed, even if leaving it
> unconfigure, it override the config variable such as XMODIFIERS in
> ~/.gnomerc or ~/.xsession, setting them to empty strings.
> 
> i think im-switch should get rid of system wide settings, (e.g, just
> reading the user config files, a dirty patch attatched)

I don't think such change would be accpeted by the maintainer.  This
patch completely removed the global configuration.  And even worse, it
doesn't fix the overriding ~/.gnomerc problem.

> or at least,
> it could be configured via debconf like most of the emacs .el packages
> (they will ask you if you'd like to eable system wide startup of the
> package).
> 
> --- 90im-switch.orig  2005-10-24 12:10:42.000000000 +0800
> +++ 90im-switch       2005-10-24 12:11:28.000000000 +0800
> @@ -21,9 +21,7 @@
>  unset XIM XIM_PROGRAM XIM_ARGS XMODIFIERS GTK_IM_MODULE

This is the problematic line.  ~/.gnomerc got read in
/etc/X11/Xsession.d/55gnome-session_gnomerc, so this unset command
overrides the settings in ~/.gnomerc.

As a workaround, I would at least like to see im-switch honor some
environment variable, like $DISABLE_IM_SWITCH or something, and if it's
set, don't do these "unset XMODIFIERS etc., and source im-switch
configurations" thing - i.e., put the whole thing in a "if [
$DISABLE_IM_SWITCH != 1 ] ... fi".

Does that sound like a sane solution?  Of course, it would be best to
implement a way to turn off im-switch, like /etc/default/im-switch or
similar, and has a debconf question to control it.

>  lang_region=$(echo $tmplang | sed -e 's/\..*//')
>  for f in $HOME/.xinput.d/${lang_region} \
> -         $HOME/.xinput.d/default \
> -         /etc/X11/xinit/xinput.d/${lang_region} \
> -         /etc/X11/xinit/xinput.d/default ; do
> +         $HOME/.xinput.d/default ; do
>      [ -r $f ] && . $f && break
>  done
>  unset lang_region

Ming
2005.10.24


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to