unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Luis Felipe <luis.felipe.la@protonmail.com>
To: Yasuaki Kudo <yasu@yasuaki.com>
Cc: help guix <help-guix@gnu.org>
Subject: Re: Can't type Japanese anymore
Date: Wed, 28 Dec 2022 23:16:54 +0000	[thread overview]
Message-ID: <xwFyNkElhNzVAFrpCQ14RPq5EsEg3F2E388VwchWziBvQGsibXc390WEEH8CkhpBQ4a-KTq1GpHI0YJn1Mzfg8PxlcOEmDNcL2PyDYFhyz0=@protonmail.com> (raw)
In-Reply-To: <jEKk5i8H5-s2mdbKqrGh4f1UtjsSkThs5SpvR2KvQOgCOne5-7BPwNkjR3HGtn9Loo4NA7pTXEjv73LAb9F3TSW9SkQVJLFoJ89_S1KooL4=@protonmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 622 bytes --]

On Wednesday, December 28th, 2022 at 21:07, Luis Felipe <luis.felipe.la@protonmail.com> wrote:

> But then I changed to my machine, went to GNOME Keyboard settings to see if I could try adding and using any of the other Japanese input methods and, lo and behold, Japanese (Anthy) was listed magically. But adding it and switching to it doesn't let me type Japanese, even with Hiragana input mode selected.
> 

> I'll restart my desktop session and hope for more magic events :)

Now Japanese (Anthy) is gone again, both from the switcher and the list of input methods in ibus-settings and GNOME Keyboard settings...

[-- Attachment #1.2: publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc --]
[-- Type: application/pgp-keys, Size: 1722 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]

  reply	other threads:[~2022-12-28 23:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-26 16:33 Can't type Japanese anymore Luis Felipe
2022-12-26 22:17 ` Yasuaki Kudo
2022-12-28 21:07   ` Luis Felipe
2022-12-28 23:16     ` Luis Felipe [this message]
2022-12-27  3:42 ` Maxim Cournoyer
2022-12-28 21:14   ` Luis Felipe
2023-01-29 19:20     ` Luis Felipe
2023-01-31 13:54       ` Maxim Cournoyer

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='xwFyNkElhNzVAFrpCQ14RPq5EsEg3F2E388VwchWziBvQGsibXc390WEEH8CkhpBQ4a-KTq1GpHI0YJn1Mzfg8PxlcOEmDNcL2PyDYFhyz0=@protonmail.com' \
    --to=luis.felipe.la@protonmail.com \
    --cc=help-guix@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.
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).