Emacs 24.3 with FCITX input methods[Resolved in 14.2]

[tsuren]

Hi zw963,
I don't use Emacs, so I cannot give you a straight solution. When I have time I will take a look at it as I use fcitx myself as well.

One good place to take a look also is AUR from Arch. They often have some patches that Slack don't have. Some patches are not useful to us as it's only Arch specific.

My second point is 'not use the ibus 1.5.5. Please use 1.4.x. You can recompile it. And youi do not need to set manually your .profile file normally. If you install also ibus-qt, you can also have export WT_IM_MODULE="ibus".

And the last point is: You might need to update the cashe for gtk2 and gtk3.

Code: Select all

gtk-query-immodules-3.0 --update-cache
gtk-query-immodules-2.0 --update-cache

[tsuren]

By the way, zw963, there should not be no difference between Salix and Slackware when talking about IMEs...

[tsuren]

Have you already read this?

[zw963]

I read this just know, because some reason wicd network manager is not worked for me.
it always tell me , password is incorrect. password is correct... wired ...

Thanks a lot for you help, what you refer to I read it already before, this problem is keep
exist in slackware many years (i use slackware three year, no use any other distro, so I don't know weather it exist in other distro.)

but, it not a big problem for me when I start to use `emacs --daemon`, because it started when boot X11, and keep exist the only
emacs process not exit, so, I use `emacsclient` to connect to this sever, always work ok, it always talk to the same emacs server process.
only very few situation, can cause emacs process input methods lost focus, at this time, I had to kill X server, reenter in, to make it work again.

Salix's problem is, when a qt application is started, above situation is happen right now, it so easy to make input method broken.
But in slackware 13/13.37/14/14.1, it not happen in this case,

And, those problem is not only relative to FCITX, it should happen for other input methods, I remember I test this some year ago.

I will tried to start daemon with `LC_CTYPE=zh_CN.UTF-8`, but I think it not the problem Salix meet anyway.

[zw963]

I read my .profile just now, it now worked for me, because I global set `LC_CTYPE=zh_CN.UTF-8` in my .profile.

I even try to set `LANG=zh_CN.UTF-8`, it still not worked for me.

I thought start a 32bit qt application change some things certainly, then start a emacs with XIM, missing somethings.

Those `start 32bit qt application change some things', is Salix particularly exist.
Those `emacs with XIM', is slackware problem.

And i read some discuss here: http://slackware.im/post/8

Add a /etc/X11/xorg.conf.d/50-fontconfig.conf, content:
```sh
<pre>
Section "Files"
FontPath "/usr/share/fonts/misc"
EndSection
</pre>
```

will fix the latter problem, But it cause salix X11 broken. I don't understood what this file does.

Another people mention:
keep `xorg.conf' Section "Files', FontPath only one line. `/usr/share/font/misc', will resolve this problem,
But I even not found this file in Salix.

Hope can help some clue for this problem.

[zw963]

I make a mistake, <pre> and </pre> is redundant.

But I change /etc/X11/xorg.conf.d/50-fontconfig.conf to

```sh
Section "Files"
FontPath "/usr/share/fonts/misc"
EndSection
```

and change /etc/X11/xorg.conf-vesa too, still not worked

Thanks.

[tsuren]

Hi zw963,

As you have already read the link, it is a bug from emacs that's never been fixed. So what you are currently doing is trying to find a workaround. So if you think your problem in this framework, you see that there is no reason for Salix or Slackware to "fix" this problem, as it is not the problem from their ends.

Have you contacted the emacs developers already on your problem?

Some files are not there by default, as it is not needed for most people, and it is normal. And it's not a problem of the distro.

I have been using IMEs (SCIM, Ibus, Fcitx) on Salix since the day one with various applications in gtk2 to qt, but I've never experienced any problem. So I am assuming that it is really an emacs' problem.

By the way, which version of fcitx are you using?

[westms]

I read my .profile just now, it now worked for me, because I global set `LC_CTYPE=zh_CN.UTF-8` in my .profile.

I even try to set `LANG=zh_CN.UTF-8`, it still not worked for me.

I thought start a 32bit qt application change some things certainly, then start a emacs with XIM, missing somethings.

Those `start 32bit qt application change some things', is Salix particularly exist.
Those `emacs with XIM', is slackware problem.

And i read some discuss here: http://slackware.im/post/8

Add a /etc/X11/xorg.conf.d/50-fontconfig.conf, content:
```sh
<pre>
Section "Files"
FontPath "/usr/share/fonts/misc"
EndSection
</pre>
```

will fix the latter problem, But it cause salix X11 broken. I don't understood what this file does.

Another people mention:
keep `xorg.conf' Section "Files', FontPath only one line. `/usr/share/font/misc', will resolve this problem,
But I even not found this file in Salix.

Hope can help some clue for this problem.

Hello zw963,
my comment is to this message and the your later (next younger) message.

You try to set C_CTYPE=zh_CN.UTF-8 and LANG=zh_CN.UTF-8

But have a look to this:

Code: Select all

locale -a | grep zh_CN
zh_CN
zh_CN.gb18030
zh_CN.gbk
zh_CN.utf8

Perhaps, you should try to set with zh_CN.utf8 instead.

Next problem:
You may have files with configurations in directory /etc/X11/xorg.conf.d
or have a configuration file named xorg.conf in /etc/X11, or combine both methods.
The file /etc/X11/xorg.conf-vesa has no meening.

File xorg.conf may contain your given lines:

Code: Select all

Section "Files"
FontPath "/usr/share/fonts/misc"
EndSection

From my /etc/X11/xorg.conf

Code: Select all

Section "Files"
	ModulePath   "/usr/lib64/xorg/modules"

##	FontPath     "/usr/share/fonts/local"  # missing
#	FontPath     "/usr/share/fonts/TTF"  # default
##	FontPath     "/usr/share/fonts/OTF"  # missing
#	FontPath     "/usr/share/fonts/Type1"  # default
#	FontPath     "/usr/share/fonts/misc"  # default
##	FontPath     "/usr/share/fonts/CID"  # missing
#	FontPath     "/usr/share/fonts/75dpi/:unscaled"  # default
#	FontPath     "/usr/share/fonts/100dpi/:unscaled"  # default
#	FontPath     "/usr/share/fonts/75dpi"  # default
#	FontPath     "/usr/share/fonts/100dpi"  # default
#	FontPath     "/usr/share/fonts/cyrillic"  # default
EndSection

The property "FontPath "/usr/share/fonts/misc" will be preset on your system too, so that the font path will not be necessary.

Maybe you will need the ModulePath to be set. If you are using a 32-bit system, the ModulePath needs to be adapted then.

Last problem:
I don't understand what you are talking about <pre> and </pre> here.

It would be glad if I have helped a little.

[zw963]

All right it seem like is emacs problem indeed, in my terminal or my browser or any I know app,
input methods is work fine.

I am not contacted the emacs developers because this bug not affect me great before now.
and if use Salix, I had to use english to write something when I work with emacs before the next
Salix/Slackware version is published, perhaps it maybe not a bad deal, my english is too pool.
I wil try to contact emacs later.

Thank you help, my fcitx version: 4.2.8.5, with gtk2 and qt support, compile myself.

do you try following process in your's Salix?? (perhaps my own fcitx is broken?)

1. start emacs with `emacs -q`
2. press whatever hotkey you set to active input method in emacs. \
3. `Ctrl-x Ctrl-c' (x and c press continuous), to exit emacs
4. start emacs again
5. hotkey is not active again.

Salix own problem can be reproduce with this:

1. add SOURCE=http://slackware.org.uk/slacky/slackware64-14.1/ to slapt-get, and update cache.
2. apt --install skype-4.3.0.37-x86_64-1sl
3. start emacs with `emacs -q', input method work well.
4. exit emacs
5. start skype
6. exit skype
7. stat emacs again, input method loss focus.

Could you please give me a workaround for Salix own problem ??

Thanks.

[tsuren]

Hi zw963
I've reproduced your first problem (not in Chinese, but in Japanese).

Have you also tested what westms suggested?

I cannot reproduce your second problem. Could you please elaborate a bit more the last line? Thanks.