[Pkg-ime-devel] Bug#705493: closed by YunQiang Su <wzssyqa@gmail.com> (Re: Bug#705493: hi)
- Subject: [Pkg-ime-devel] Bug#705493: closed by YunQiang Su <wzssyqa@gmail.com> (Re: Bug#705493: hi)
- From: support@oeko.net (Toni Mueller)
- Date: Tue, 30 Jul 2013 19:23:40 +0200
- Message-id: <[🔎] 20130730172339.GB5158@spruce.wiehl.oeko.net>
- In-reply-to: <handler.705493.D705493.13752034619750.notifdone@bugs.debian.org>
- References: <CAKcpw6Wb=mJzqk6_XzmwGcce4-i1aPReSLa6GkvxEmQ5=pU9XA@mail.gmail.com> <20130415162800.15667.69028.reportbug@spruce.wiehl.oeko.net> <handler.705493.D705493.13752034619750.notifdone@bugs.debian.org>
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.
I have found a workaround, though: Often, I regain the ability to use
fcitx by twiddling the input method settings of the "surrounding"
terminal program.
This is still unsatisfactory, but no longer a show-stopper.
FWIW, when I decide to use fcitx, I run this command before firing up my
X session after setting my environment variables properly (although as
part of a script):
$ im-config -n fcitx
Kind regards,
--Toni++
Reply to: