From: jonetsu <jonetsu@teksavvy.com>
To: help-gnu-emacs@gnu.org, Rusi <rustompmody@gmail.com>
Subject: Re[4]: <Multi_key> is undefined
Date: Thu, 09 Apr 2015 15:53:25 -0400 [thread overview]
Message-ID: <bac3d91bef51e2dcbe84cc1c4316ca48@teksavvy.com> (raw)
In-Reply-To: <925493db-8d9b-4182-bda2-f0084bc4cbfa@googlegroups.com>
> From: Rusi <rustompmody@gmail.com>
> Date: 04/08/15 23:00
> Subject: Re: Re[2]: <Multi_key> is undefined
> 1. Try starting emacs with unset XMODIFIERS and see if the problem goes away
I have tried:
XMODIFIERS="" emacs
and:
/usr/bin/env -u XMODIFIERS emacs
And both of them get rid of the '<Multi_key> is undefined' emacs message, but that's it. The letter with the accent, as it appears at the (k)console, firefox, sylpheed-claws client, etc... is not shown in emacs.
> 2. Why/what do you use ibus for?
Chinese. Well, I try, as it seems to be quite broken in Linux Mint 17. Either it is broken, or the OS input method has seen some changes. emacs does have a Chinese input mode these days although it is really not nice to use. I'm used to ibus and emacs and have written a lot of text easily that way, on a previous OS (Linux Mint 14, which I still boot when I have specifically Chinese text to write). Now I would like to use a more recent OS, and add actual pinyin notation alongside Chinese hanzi.
So, so far, no, unsetting XMODIFIERS does not work.
next prev parent reply other threads:[~2015-04-09 19:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.208.1428504833.904.help-gnu-emacs@gnu.org>
2015-04-08 17:21 ` <Multi_key> is undefined Emanuel Berg
2015-04-08 18:59 ` Re[2]: " jonetsu
2015-04-09 0:44 ` Stefan Monnier
[not found] ` <mailman.230.1428519467.904.help-gnu-emacs@gnu.org>
2015-04-09 2:57 ` Re[2]: " Rusi
2015-04-09 19:53 ` jonetsu [this message]
2015-04-10 2:49 ` Eric Abrahamsen
[not found] ` <mailman.329.1428609127.904.help-gnu-emacs@gnu.org>
2015-04-10 16:20 ` Re[4]: " Rusi
2015-04-10 17:37 ` Stefan Monnier
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bac3d91bef51e2dcbe84cc1c4316ca48@teksavvy.com \
--to=jonetsu@teksavvy.com \
--cc=help-gnu-emacs@gnu.org \
--cc=rustompmody@gmail.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).