unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: guix-devel <guix-devel@gnu.org>
Subject: Trying to fix IBus
Date: Wed, 10 Aug 2016 23:09:21 +0200	[thread overview]
Message-ID: <87lh04covy.fsf@elephly.net> (raw)

Hi Guix,

IBus is still broken.  That’s primarily because we don’t generate an
input method modules cache file that GTK+ looks for.  The cache file for
GTK3 can be generated with

    gtk-query-immodules-3.0 /path/to/profile

Then we point the environment variable GTK_IM_MODULE_FILE to the file.
I tried this, rebooted, and noticed that now any GTK2 application
crashes.  That’s because GTK_IM_MODULE_FILE is used by both major GTK
versions, but the input method modules are not compatible with both
versions.

NixOS encountered the same problem:

    https://github.com/NixOS/nixpkgs/pull/14568

I don’t like their solution to set a variable NIX_PROFILES and let GTK
look for immodule files in each of the directories.  Instead, I think we
should patch both GTK versions to respect GUIX_GTK2_IM_MODULE_FILE and
GUIX_GTK3_IM_MODULE_FILE, and generate the immodule cache files in a
profile hook.

We did something similar before with GUIX_GTK2_PATH and GUIX_GTK3_PATH.

Upstream doesn’t want to accept patches like this because they are
moving away from dynamically switchable input method modules.  Instead
they will just support a single input method system per platform.  This
means that ultimately we will be able to drop these patches.

What do you think?  Is this acceptable/reasonable?

~~ Ricardo

             reply	other threads:[~2016-08-10 21:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10 21:09 Ricardo Wurmus [this message]
2016-08-10 22:35 ` Trying to fix IBus Alex Griffin
2016-08-11  5:50   ` Ricardo Wurmus
2016-08-11  8:41 ` Chris Marusich
2016-08-11 10:14   ` Ricardo Wurmus
2016-08-11 10:51     ` Chris Marusich
2016-08-11 13:12       ` Ricardo Wurmus
2016-08-11 13:17         ` Ricardo Wurmus
2016-08-12 16:34           ` 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=87lh04covy.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@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.
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).