reopen 709921
severity 709921 normal
notfound 709921 0.21
notfound 709921 0.22-1
notfound 709921 0.22-2
notfound 709921 0.22-3
thanks

(I think this was not bug of im-config after all)

On Tue, Jun 04, 2013 at 12:51:53AM +0800, Aron Xu wrote:
...
> > Did you restarted X session before testing?  I am a bit lost....
...
> Got it working after rebooting the machine, restart X seems does not
> work. I'm using systemd as init, but not sure whether this can be
> related.

This made me think again.

I initially thought Aron's analysis is 100% right.

| The problem is valid for the detection code
| of GTK2, GTK3, Qt4, and Clutter IM modules.
| 
|  16 for IM_CONFIG_MARKER in /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so \
|  17                         /usr/lib/gtk-2.0/*/immodules/im-fcitx.so ; do

I agree this may make some people worry.  When I implemented, I knew
what I was doing.  But after a while, I forgot that kind of details.  So
when Aron said, I even got tricked myself.  These *s, if they do not
much produce /usr/lib/*/gtk-2.0/*/immodules/im-fcitx.so as is.  But the
following lines check if they really exist.  So bogus name with * means
file does not exist and keep on checking.i

So the code in stable 0.21 is OK.

Of course, starting subshell with $(...) makes program slower.  I think
that was why I chose this style of coding.  But now that I think of
this, speed is non-critical and easy to understand code is good for
maintenance.

Here is my check for 0.21   .... it works to set up fcitx :-)

$ dpkg -l im-config
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version      Architecture Description
+++-==============-============-============-=================================
ii  im-config      0.21         all          Input method configuration framew
$ env|grep fcitx
XMODIFIERS=@im=fcitx
QT4_IM_MODULE=fcitx
GTK_IM_MODULE=fcitx




Regards,

Osamu

PS: Once I see this updates BTS, I will close this bug.


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

Reply via email to