all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: tumashu <tumashu@163.com>
Cc: guix <guix-devel@gnu.org>
Subject: Re: Integrating different input methods into Guix
Date: Mon, 23 Jan 2017 01:32:11 +0100	[thread overview]
Message-ID: <20170123013211.22b9fb84@scratchpost.org> (raw)
In-Reply-To: <83607e0.462.159c89d1385.Coremail.tumashu@163.com>

Hi,

I understand. For now, let's see what the others say about the proposed design.

If you want to just set the environment variables in your user session, you can just edit ~/.bash_profile and invoke im-config there (maybe unchanged - although it bothers me that it then would invoke random versions of the input methods - which can change depending on what's installed right now).

But it would be nicer if the login screens used the input methods, too. That would be possible by either writing a service, or, as a quick fix, by adding the environment variables to gnu/services/xorg.scm :

              (fork+exec-command
               (list (string-append #$slim "/bin/slim") "-nodaemon")
               #:environment-variables
               (list (string-append "SLIM_CFGFILE=" #$slim.cfg)
                     "IM_CONFIG_xyz=FIXME"
                     #$@(if theme
                            (list #~(string-append "SLIM_THEMESDIR=" #$theme))
                            #~())))))

  reply	other threads:[~2017-01-23  0:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-22  0:57 A question about im-config tumashu
2017-01-22  1:15 ` Danny Milosavljevic
2017-01-22  2:39   ` tumashu
2017-01-22  8:06     ` Integrating different input methods into Guix Danny Milosavljevic
2017-01-22 23:57       ` tumashu
2017-01-23  0:32         ` Danny Milosavljevic [this message]
2017-01-23  6:38           ` Re:Re: Integrating " tumashu
2017-01-26  8:02       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170123013211.22b9fb84@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=guix-devel@gnu.org \
    --cc=tumashu@163.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.