all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bernard Hurley <bernard@marcade.biz>
To: Glenn Morris <rgm@gnu.org>
Cc: 12614@debbugs.gnu.org
Subject: bug#12614: 24.2; Ibus does not work properly with Ido find-file
Date: Wed, 10 Oct 2012 13:19:10 +0100	[thread overview]
Message-ID: <20121010121910.GA29024@marcade.biz> (raw)
In-Reply-To: <hvpq4qsuq9.fsf@fencepost.gnu.org>

On Wed, Oct 10, 2012 at 02:32:14AM -0400, Glenn Morris wrote:
> 
> Thanks for the detailed report, but ibus is not part of Emacs.
> Have you tried reporting this to whoever maintains it?
> Or do you think this is actually an Ido problem? (That is part of Emacs.)

That's difficult to say without knowing what's actually causing 
the problem. It seems that ibus is returning "too early" and it
is difficult to see why this should happen if nothing is
interfering with it. When I type "m" it looks to ibus as if "m "
or "m1" or something like that has been typed. This extra 
character must be generated by Ido somehow as when ido-mode is
not active C-x C-f works just fine with ibus input. Whether one
considers this a bug or not might depend on whether this
behaviour affects other emacs packages. If it doesn't then one
might take the view that other packages should work round it.

I will get in touch with the ibus maintainers. Incidentally 
Ibus is the more or less standard way of inputting CJK characters
on Linux systems. I know several professional translators who
use it. The unicode packages make it very easy to set up fonts
exactly how you want them so I would suggest ibus really ought
to be part of Emacs.

Bernard.





      reply	other threads:[~2012-10-10 12:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10  1:56 bug#12614: 24.2; Ibus does not work properly with Ido find-file Bernard Hurley
2012-10-10  6:32 ` Glenn Morris
2012-10-10 12:19   ` Bernard Hurley [this message]

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=20121010121910.GA29024@marcade.biz \
    --to=bernard@marcade.biz \
    --cc=12614@debbugs.gnu.org \
    --cc=rgm@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.