From: Caleb Herbert <csh@bluehome.net>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Application Setup on Trisquel
Date: Fri, 10 Nov 2017 15:29:01 -0600 [thread overview]
Message-ID: <1510349341.3633.25.camel@leela> (raw)
In-Reply-To: <87zi7upuy9.fsf@gmail.com>
On Thu, 2017-11-09 at 13:05 -0800, Chris Marusich wrote:
> This sounds very similar to
>
> https://lists.gnu.org/archive/html/help-guix/2017-05/msg00069.html
>
> in which the interaction between Guix-installed packages (emacs, in my
> case) and the XDG_DATA_DIRS environment variable caused the UI
> (including icons) to display incorrectly. It would be nice to solve
> this in general for Guix-installed applications on foreign distros. Do
> you have any ideas about how we can solve it?
I don't know how to solve it, but I tried what was done in that post,
and it seemed to help.
env -u XDG_DATA_DIRS icecat &
env -u XDG_DATA_DIRS youtube-dl-gui &
IceCat looked much better:
http://bluehome.net/csh/screenshot/2017/11/10/icecatprofile
http://bluehome.net/csh/screenshot/2017/11/10/icecatwindow
youtube-dlG, however, looked the same:
http://bluehome.net/csh/screenshot/2017/11/10/youtubedlgui
> "/usr/share/" entry from XDG_DATA_DIRS. You were able to solve your
> problem by adding ${HOME}/.guix-profile/share to the front of XDG_DATA_DIRS
> and adding the foreign distro's XDG_DATA_DIRS (including "/usr/share/"
> to the end). I feel like these clues are pointing to something, but I'm
> not yet sure what. Do you have any good ideas?
You'd have to ask ADFENO. I didn't think too much about the changes I
made to my system. I just looked at his instructions, determined if
they were harmless, and followed them.
> displayed icons, locales, etc.) . However, asking users to configure
> XDG_DATA_DIRS seems significantly more complicated, due to problems like
> these, and also like bug 26202:
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26202
I agree. I'm just a luser. I don't have a spare system to do
experiments on, and I don't want to be doing experiments on my only
device.
> > Remaining hurdles:
> > * Buttons don't show up, themes don't match:
> > https://lut.im/g7za20HA8Z/U8CWURMKf3X0a1GI.png
>
> Could this be the same issue that I saw with emacs?
Yes.
> > * Fcitx Mozc input method for Japanese does not work in Guix apps
>
> Can you tell us more about your use case? Are you trying to install
> fcitx etc. via Guix, and then use it to type in Japanese within
> Guix-installed applications (do they use GTK, or something else)?
No. I tried doing that, and Fcitx wouldn't run properly because it
didn't like the fact that Trisquel had its own ibus running.
> Or
> did you install fcitx etc. using the foreign distro's package manager
> (e.g., apt-get), and now you are trying to use that IME to type in
> Japanese within Guix-installed apps?
Yes, this is what I did.
sudo apt install fcitx fcitx-mozc
I can type Japanese in Trisquel apps, but not in Guix apps.
Also, Trisquel's Fcitx will let me type Japanese but not any other
language. Greek is available, but I still get "aoeu" when I switch to
it.
> The interaction between an IME and
> its environment is tricky to get right and depends on a lot of factors,
> so I expect it might require a non-trivial amount of work to make it so
> that all Guix-installed apps will correctly make use of an IME that is
> installed and managed by the foreign distro.
I would gladly use Guix's Fcitx, because its Mozc is newer and lets you
type もも (momo, "peach") to get 🍑 (":peach:"). But, as mentioned
above, it doesn't play nice with Trisquel's ibus.
> FWIW, I have been able to get Japanese input working in GuixSD in all
> apps using ibus and ibus-anthy.
##japanese on Freenode says Anthy is abandoned, so they recommend Fcitx.
Re GuixSD, I should take the hard drive out of my old laptop and install
GuixSD to try it out.
next prev parent reply other threads:[~2017-11-10 21:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 18:12 Application Setup on Trisquel Caleb Herbert
2017-10-24 21:16 ` Ludovic Courtès
2017-10-24 22:04 ` Caleb Herbert
2017-10-26 17:54 ` Ludovic Courtès
2017-10-27 1:02 ` Chris Marusich
2017-10-24 23:33 ` Caleb Herbert
2017-10-24 23:44 ` Caleb Herbert
2017-10-26 17:52 ` Ludovic Courtès
2017-10-26 20:05 ` Caleb Herbert
2017-10-25 0:36 ` Mikhail Kryshen
2017-10-26 17:53 ` Ludovic Courtès
2017-10-27 3:29 ` Caleb Herbert
2017-11-08 6:39 ` Caleb Herbert
2017-11-09 21:05 ` Chris Marusich
2017-11-10 21:29 ` Caleb Herbert [this message]
2017-11-12 14:55 ` Adonay Felipe Nogueira
2017-11-12 17:09 ` Adonay Felipe Nogueira
2017-11-12 13:02 ` Adonay Felipe Nogueira
2017-11-02 2:59 ` Mark H Weaver
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=1510349341.3633.25.camel@leela \
--to=csh@bluehome.net \
--cc=cmmarusich@gmail.com \
--cc=help-guix@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.
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).