Hi Aron,

On Wed, Jul 31, 2013 at 09:34:08PM +0800, Aron Xu wrote:
> On Wed, Jul 31, 2013 at 1:23 AM, Toni Mueller <supp...@oeko.net> wrote:
> > On Tue, Jul 30, 2013 at 05:00:09PM +0000, Debian Bug Tracking System wrote:
> >> This is not a bug, you should use im-config to set proper env.
> >> include GTK_IM_MODULES, QT4_IM_MODULES etc
> >
> > I actually do this. I lose the ability to use fcitx in certain programs
> > in the middle of a session, at random points. Like I work for, say, an
> > hour, and suddenly, the ability to use fcitx with certain (console)
> > programs goes away in the middle of said session.
> 
> This is a bug in im-config, because im-config now launch input method
> after dbus is successfully initialized. But there is problem that it
> exports those environmental variables at that time, so that
> applications that have components spawned directly by the desktop
> dbus-daemon process will not have those environmental variables set.

I am not sure that I understand you. I run this script during my
(console) login script (usually, ~/.bash_profile, as ". ./bin/im-start"):


------------------------------------------- cut
# get the desired config:
sans=""
IME=scim
echo -n "Use Scim / IBUS / fcitx (default: fcitx)? "
read imeans

case "$imeans" in
        "scim")
            IME=scim
            ;;
        "ibus")
            IME=ibus
            ;;
        ""|"fcitx")
            IME=fcitx
            ;;
        *)
            echo "Can't configure - setting IME to None"
            IME=x
            ;;
esac

if [ X"${IME}" = X"scim" ]; then
        XMODIFIERS="@im=SCIM"
        export XMODIFIERS
        #GTK_IM_MODULE="scim"
        GTK_IM_MODULE="xim"
        QT_IM_MODULE="xim"
        export GTK_IM_MODULE
        export QT_IM_MODULE
        im-config -n scim
        echo "Configuring scim"
elif [ X"${IME}" = X"ibus" ]; then 
        XMODIFIERS="@im=ibus"
        export XMODIFIERS
        GTK_IM_MODULE="ibus"
        QT_IM_MODULE="ibus"
        export GTK_IM_MODULE
        export QT_IM_MODULE
        im-config -n ibus
        echo "Configuring ibus"
elif [ X"${IME}" = X"fcitx" ]; then 
        XMODIFIERS="@im=fcitx"
        export XMODIFIERS
        GTK_IM_MODULE="xim"
        QT_IM_MODULE="xim"
        export GTK_IM_MODULE
        export QT_IM_MODULE
        im-config -n fcitx
        echo "Configuring fcitx"
else
        echo "Unsupported input method, refuse to configure!"
fi
------------------------------------------- cut

After that, I run the appropriate daemon from my .xinit file before
starting up the window manager.

Therefore, every program should have the correct environment variables
set. I just verified that im-config is also not a running process, so
I currently do not understand how it could create havoc with my
environment.



Kind regards,
--Toni++


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to