From: iyzsong@member.fsf.org (宋文武)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Typing on GuixSD in languages other than English
Date: Sun, 10 Apr 2016 17:47:01 +0800 [thread overview]
Message-ID: <878u0ln6cq.fsf@member.fsf.org> (raw)
In-Reply-To: 宋文武's message of "Sun\, 10 Apr 2016 13\:43\:39 +0800"
iyzsong@member.fsf.org (宋文武) writes:
> Chris Marusich <cmmarusich@gmail.com> writes:
>
>> Awesome! Where you able to get this working? I've tried installing it
>> From the version you pushed, and I still can't get it to work. Even
>> when I set all the environment variables mentioned, and I install all
>> the packages (ibus, ibus-anthy, and anthy) to my profile. If you got it
>> working, I'd like to know how so I can set it up on my end, too.
Yes, I only tested in xterm.
set the environemnt variables, run ‘ibus-daemon –-xim -v’.
then use ‘ibus-setup’ to add ‘Japanese - Anthy’.
in xterm, ‘Super+Space’ work fine.
For GTK+ applications, I have to generate the ‘immodules.cache’ file:
--8<---------------cut here---------------start------------->8---
GTK_IM_MODULE_FILE=/tmp/immodules.cache gtk-query-immodules-3.0 -–update-cache
GTK_IM_MODULE_FILE=/tmp/immodules.cache gtk3-demo –-run search_entry
--8<---------------cut here---------------end--------------->8---
With the cache (it contains ibus), it will work.
next prev parent reply other threads:[~2016-04-10 9:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-02 21:51 Typing on GuixSD in languages other than English Chris Marusich
2016-04-03 1:00 ` 宋文武
2016-04-03 4:17 ` Chris Marusich
2016-04-04 0:26 ` Chris Marusich
2016-04-04 2:26 ` Luis Felipe López Acevedo
2016-04-04 5:37 ` Chris Marusich
2016-04-04 14:36 ` Luis Felipe López Acevedo
2016-04-09 1:41 ` 宋文武
2016-04-09 19:38 ` Chris Marusich
2016-04-10 9:47 ` 宋文武 [this message]
2016-04-13 1:48 ` Chris Marusich
2016-04-17 8:26 ` Chris Marusich
2016-04-18 7:27 ` Ricardo Wurmus
2016-04-04 20:10 ` Ricardo Wurmus
2016-04-05 6:48 ` Chris Marusich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878u0ln6cq.fsf@member.fsf.org \
--to=iyzsong@member.fsf.org \
--cc=cmmarusich@gmail.com \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).