Re: [tlug] ALERT: fcitx-mozc is lovely

[Scott Robbins <scottro@example.com>]

On Wed, Jan 27, 2016 at 09:38:51AM +0900, CL wrote:

> Instructions are Not Quite Right for Jessie KDE (and maybe also due to 
> using true nvidia drivers instead of nouveau ... or user stupidity ... 
> or a combination of those factors).
> 
Ah, I never use KDE. With Debian (and others that don't have a default
desktop), I usually test with dwm or openbox.



> 1.    No xinitrc file BUT there is an xinput file which I modified and 
> seems to only accept input from Input Method.  Attempts to modify the 
> file by adding text to the created file only earned me a scolding from 
> Input Method setup and I was told to erase xinput and start over.

A $HOME/.xinitrc (note the period) may not be there if you use KDM or
whatever graphic login manager you choose. (I thind I do mention something
to the effect that if one is using a GUI login, I'm not sure what files to
edit.


> 
> 2.    Creating an xinput file changes nothing.
> 
> 3.    I admit to being unsure which windows manager I am using other 
> than "the one that was installed and just works".
> 
> 4.    The nvidiarc file does not look as though it is the right x 
> control folder to be adding stuff into as contents deal more with color 
> intensity and GPU temperature monitoring.
> 
> 5.   Adding the "export" and "fcitx" lines to bashrc leads to a 
> configurable installation upon reboot.

Ok, they would be read.  That isn't where I would add them though.

> BUT
> 
> I cannot switch inputs from the keyboard (I want to use L_SHFT + L_ALT 
> to start and switch, like MS-IME) and still have to mouse click the 
> keyboard icon to switch language inputs manually.  In this regard 
> nothing much is different from the working ibus installation I nuked to 
> install this.
> 
> Suggestions?  ... (other than "Have you tried Windows 10" of course).
> 

Heh. I haven't tried input in Windows 10. To be honest, no, I've only
tested it for my needs, limited to staying with the default ctl+shift.  

For starting it in X, if you're using a log in manager, I think the
important thing is that you have these variables set. I'm not sure where
the best place to set them would be in KDE.  

For me, it was the opposite, on most distributions I was using, ibus was
becoming less reliable as far as using the keyboard. 

There may be (judging from the Arch wiki) a kde-fcitx module, though I
don't know how to use it, and the Arch wiki gives no explanation.   

A quick google doesn't show a way to change the default key combo, but I
suspect it exists. 

I see that in Fedora, fcitx-config-gtk opens a dialog where it looks as if
you can change the default input keys. 


-- 
Scott Robbins
PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6