unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: yasu@yasuaki.com
Cc: guix-devel@gnu.org
Subject: Re: Japanese Input wont't without manually adding environmental variables?
Date: Sat, 07 Nov 2020 10:23:49 +0100	[thread overview]
Message-ID: <01bb3fc700006f6edbc1919f5cd81484410a9e74.camel@student.tugraz.at> (raw)
In-Reply-To: 8c9bc8edbc5c0b9e06f0bd66b1069d4a5c71eea2.camel@yasuaki.com

Hello, yasu

I recently submitted #44354, which would set GUIX_GTK*_IM_MODULE_FILE
from the system configuration.  Once this patch is merged, you should
be able to add ibus and ibus-anthy to your operating-system packages
and have them picked up from there by gnome.

Note, that this patch would as it is currently likely only set
GUIX_GTK3_IM_MODULE_FILE, because the gnome package does not contain
anything linked against gtk+-2.  If that is a concern, you can add an
application that does to it.  Mine currently looks like this:

```
  (package
    (inherit gnome)
    (propagated-inputs
     `(,@(package-propagated-inputs gnome)
       ;; IBus
       ("ibus" ,ibus)
       ("ibus-anthy" ,ibus-anthy)
       ;; World
       ("dconf-editor" ,dconf-editor)
       ("evolution" ,evolution)
       ("evolution-data-server" ,evolution-data-server)
       ("gitg" ,gitg)
       ("gnome-tweaks" ,gnome-tweaks)
       ("polari" ,polari)
       ("seahorse" ,seahorse))))
```

[As you can see, just ibus and a few more Gnome packages, but none
using Gtk+ 2.]

Best regards,
Leo



             reply	other threads:[~2020-11-07  9:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-07  9:23 Leo Prikler [this message]
2020-11-07 12:07 ` Japanese Input wont't without manually adding environmental variables? yasu
  -- strict thread matches above, loose matches on Subject: below --
2020-11-07  6:46 yasu
2020-11-07  8:41 ` 宋文武
2020-11-07  8:49   ` yasu
2020-11-07 10:43     ` 宋文武

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=01bb3fc700006f6edbc1919f5cd81484410a9e74.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).