From: 宋文武 <iyzsong@outlook.com>
To: yasu <yasu@yasuaki.com>
Cc: guix-devel@gnu.org
Subject: Re: Japanese Input wont't without manually adding environmental variables?
Date: Sat, 07 Nov 2020 16:41:52 +0800 [thread overview]
Message-ID: <PU1PR04MB23109A3821AD0A6B50AA7417A3EC0@PU1PR04MB2310.apcprd04.prod.outlook.com> (raw)
In-Reply-To: <889300f32061393053a64f45b7005fae9d5c41e9.camel@yasuaki.com> (yasu@yasuaki.com's message of "Sat, 07 Nov 2020 15:46:34 +0900")
yasu <yasu@yasuaki.com> writes:
> Hi!
>
> After installing packages ibus and ibus-anthy , I thought I would be able to type Japanese - but I had to follow the tip below and manually add these variables to make it work.
> Would this be considered a bug?
Yes, guix lack supports for input methods.
>
> https://www.mail-archive.com/help-guix@gnu.org/msg08282.html
>
> export GUIX_GTK2_IM_MODULE_FILE="$HOME/.guix-profile/lib/gtk-2.0/2.10.0/immodules-gtk2.cache"
> export GUIX_GTK3_IM_MODULE_FILE="$HOME/.guix-profile/lib/gtk-3.0/3.0.0/immodules-gtk3.cache"
>
For these kind of environment variables, we usually set them in
'.guix-profile/etc/profile' via 'native-search-paths' of a package.
But adding 'GUIX_GTK3_IM_MODULE_FILE' to the 'native-search-paths' of
'gtk+' is not good enough or won't solve this issue as we usually don't
install 'gtk+' into the profile. I'd like to find another way set them,
could be add some code to '(guix profiles)' with the 'gtk-im-modules'
profile hook. Need more thinking...
In the meantime, we have to set those environment variables manually..
next prev parent reply other threads:[~2020-11-07 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 6:46 Japanese Input wont't without manually adding environmental variables? yasu
2020-11-07 8:41 ` 宋文武 [this message]
2020-11-07 8:49 ` yasu
2020-11-07 10:43 ` 宋文武
-- strict thread matches above, loose matches on Subject: below --
2020-11-07 9:23 Leo Prikler
2020-11-07 12:07 ` yasu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=PU1PR04MB23109A3821AD0A6B50AA7417A3EC0@PU1PR04MB2310.apcprd04.prod.outlook.com \
--to=iyzsong@outlook.com \
--cc=guix-devel@gnu.org \
--cc=yasu@yasuaki.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.