all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: iyzsong@outlook.com
To: 45064@debbugs.gnu.org
Cc: 宋文武 <iyzsong@member.fsf.org>
Subject: [bug#45064] [PATCH 0/2] Set environment variables for GTK+ input methods via profile startup files
Date: Sun,  6 Dec 2020 13:40:06 +0800	[thread overview]
Message-ID: <TYAP286MB018580C92BF3E9783BD56362A3CF0@TYAP286MB0185.JPNP286.PROD.OUTLOOK.COM> (raw)

From: 宋文武 <iyzsong@member.fsf.org>

Hello, Guix!

To use GTK+ input methods, currently we need set
‘GUIX_GTK2_IM_MODULE_FILE’ and ‘GUIX_GTK3_IM_MODULE_FILE’ manually in
.xsession or .bash_profile, we also having a patch [1] that set them
for gnome via ‘gnome-desktop-service-type’.  But I think the right
place to set them is the ‘gtk-im-modules’ profile hook, so the first
patch make ‘etc/profile’ source files in ‘etc/profile.d/*.sh’, and the
second patch add ‘etc/profile.d/gtk2-im-modules.sh’ and
‘etc/profile.d/gtk3-im-modules.sh’.  The first patch is also useful
for packages that provide profile startup files (eg: nix).

Thanks!

[1] <https://issues.guix.gnu.org/44354>

Sou Bunnbu (宋文武) (2):
  profiles: Load application specific startup files.
  profiles: gtk-im-modules: Set environment variables for input methods.

 guix/build/profiles.scm | 13 ++++++++++++-
 guix/profiles.scm       | 12 ++++++++++--
 2 files changed, 22 insertions(+), 3 deletions(-)

-- 
2.29.2





             reply	other threads:[~2020-12-06  6:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-06  5:40 iyzsong [this message]
2020-12-06  6:15 ` [bug#45064] [PATCH 1/2] profiles: Load application specific startup files iyzsong
2020-12-07 12:09 ` [bug#45064] [PATCH 0/2] Set environment variables for GTK+ input methods via profile " Leo Prikler
2020-12-07 13:55   ` 宋文武
2020-12-07 14:47     ` Leo Prikler

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=TYAP286MB018580C92BF3E9783BD56362A3CF0@TYAP286MB0185.JPNP286.PROD.OUTLOOK.COM \
    --to=iyzsong@outlook.com \
    --cc=45064@debbugs.gnu.org \
    --cc=iyzsong@member.fsf.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 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.