Description of problem: My system uses GNOME 3.6, pt_BR.utf8 locale and Portuguese (Brasil) keyboard layout. The locale and keyboard settings were made using the gnome control center. With this setup emacs can't process dead keys as it did in F16. Whenever I type a dead key the error "<dead-acute> is undefined appears". I'm assuming this is related to the GNOME and ibus integration. Version-Release number of selected component (if applicable): emacs-24.2-6.fc18.x86_64 ibus-1.5.1-2.fc18.x86_64 How reproducible: Deterministic
A workaround is to put (require 'iso-transl) in your ~/.emacs file.
I can show acute + c with emacs on en_US.UTF-8 . If you use gnome-shell, I think you need to configure a compose key with 'gnome-control-center keyboard' command.
I can't make it work not even in the en_US.UTF-8 locale. What keyboard layout did you use? If you want to reproduce this bug but and don't have a Brazilian keyboard lying around, try the "English (US, international with dead keys)" layout. In my locale (pt_BR) the tradition is to use dead keys, not a compose key.
(In reply to comment #3) > If you want to reproduce this bug but and don't have a Brazilian keyboard > lying around, try the "English (US, international with dead keys)" layout. I can show acute e with "English (US, international with dead keys)" on en_US.UTF-8 if I type apostrophe + e, I can show acute e with "English (US)" on en_US.UTF-8 if I type compose + apostrophe + e. I assigned Windows key as compose key with gnome-control-center keyboard.
*** Bug 918747 has been marked as a duplicate of this bug. ***
Well, so it is apparently hard to reproduce. I can reproduce with the following steps: * Make a fresh installation of F18 in a VM, using the en_US locale and the default us keyboard. * Install emacs but do not apply any other package update. * Setup the English (US, international with dead keys) and a compose key. * Start smacs With "English (US, international with dead keys)" if I type apostrophe I get "<dead-acute> is undefined" in minibuffer. With "English (US)" if I type compose + apostrophe I get "<Multi-key> is undefined" in minibuffer. After applying all current updates the result is the same.
Are you able to reproduce your problem with gedit?
No, gedit works perfectly. It's only emacs and jabref (maybe other Java apps, but I have not tested).
One more discovery. The variable XMODIFIERS is currently: [teste@localhost ~]$ echo $XMODIFIERS @im=ibus If I fire emacs with: [teste@localhost ~]$ XMODIFIERS="" emacs dead keys work.
(In reply to comment #8) > No, gedit works perfectly. It's only emacs and jabref (maybe other Java > apps, but I have not tested). I cannot reproduce your problem. > Whenever I type a dead key the error "<dead-acute> is undefined appears". What does the error message mean? Why does your emacs express "undefined"? I see neither the dead-acute nor Multi-key message. > * Make a fresh installation of F18 in a VM, using the en_US locale and the default us keyboard. And did you update the latest ibus with 'yum install ibus'? I expect you run ibus-daemon and emacs on en_US.UTF-8 but not en_US.
(In reply to comment #10) > I cannot reproduce your problem. Have you tried a fresh installation on a VM? I'm suspecting it might be related to the default package set of a fresh install. Maybe something is missing, but already installed in your machine. > > What does the error message mean? Why does your emacs express "undefined"? > I see neither the dead-acute nor Multi-key message. > I have no idea. Maybe we can ask the emacs packager for help? > > * Make a fresh installation of F18 in a VM, using the en_US locale and the default us keyboard. > > And did you update the latest ibus with 'yum install ibus'? Initially no. Now, I have updated on the test machine to ibus-1.5.1-2.fc18 and the problem persists. > I expect you run ibus-daemon and emacs on en_US.UTF-8 but not en_US. When I said en_US I wanted to say: "Make a fresh installation using English (US) as language". The resulting locale, according to the $LANG variable is en_US.UTF-8.
Same as bug#917130: Set Portuguese (Brazil) keyboard in Gnome panel. With the following command lines env XMODIFIERS="" LC_ALL=pt_BR.UTF-8 emacs env XMODIFIERS=@im=none LC_ALL=pt_BR.UTF-8 emacs env -u XMODIFIERS LC_ALL=pt_BR.UTF-8 emacs dead keys work perfectly in Emacs: The key to the right of ‘P’ followed by ‘c’ inserts ç. With the following command line: env XMODIFIERS=@im=ibus LC_ALL=pt_BR.UTF-8 emacs a) If ibus is not running: “<dead_acute> is undefined” error in emacs b) If ibus is running: dead keys work partly, but not for pt_BR.UTF-8 locale, the key to the right of ‘P’ followed by ‘c’ inserts ć. With the following command line: env XMODIFIERS=@im=foobar LC_ALL=pt_BR.UTF-8 emacs one always gets the “<dead_acute> is undefined” error in emacs (unless an XIM server named “foobar” existed, than it might do whatever that XIM server does with the dead keys).
If Emacs actually "sees" the dead keys, they are undefined "of course". But when the dead keys work correctly, Emacs does not see them, Emacs then only sees the result of the dead key handling.
*** This bug has been marked as a duplicate of bug 917130 ***
(In reply to comment #12) > dead keys work perfectly in Emacs: > > The key to the right of ‘P’ followed by ‘c’ inserts ç. I expect to use 'us' layout. apostrophe is next to ';' instead. You may use 'jp' layout. > > With the following command line: > > env XMODIFIERS=@im=ibus LC_ALL=pt_BR.UTF-8 emacs > > a) If ibus is not running: “<dead_acute> is undefined” error in emacs > b) If ibus is running: dead keys work partly, but not for pt_BR.UTF-8 > locale, the key to the right of ‘P’ followed by ‘c’ inserts ć. I don't talk about 'c' yet but 'e'. If you say 'c', you need to run ibus on pt_BR.UTF-8 but not emacs on pt_BR.UTF-8.
(In reply to comment #15) > (In reply to comment #12) > > dead keys work perfectly in Emacs: > > > > The key to the right of ‘P’ followed by ‘c’ inserts ç. > > I expect to use 'us' layout. apostrophe is next to ';' instead. > You may use 'jp' layout. No, Portuguese (Brasil) layout. http://en.wikipedia.org/wiki/Keyboard_layout#Brazil On this layout, the apostrophe is at the top left, but there is also a “dead_acute” on the key to the right of the “P” key. > > With the following command line: > > > > env XMODIFIERS=@im=ibus LC_ALL=pt_BR.UTF-8 emacs > > > > a) If ibus is not running: “<dead_acute> is undefined” error in emacs > > b) If ibus is running: dead keys work partly, but not for pt_BR.UTF-8 > > locale, the key to the right of ‘P’ followed by ‘c’ inserts ć. > > I don't talk about 'c' yet but 'e'. > If you say 'c', you need to run ibus on pt_BR.UTF-8 but not emacs on > pt_BR.UTF-8. Ah, yes, you are right, that is very nice! I thought ibus has the same dead key support for all locales, but in fact it seems to be locale dependent! So when I use env XMODIFIERS=@im=ibus LC_ALL=pt_BR.UTF-8 emacs and ibus is running in pt_BR.UTF-8 locale, then the key an the Portuguese (Brazil) layout to the right of ‘P’ followed by ‘c’ inserts ‘ç’ perfectly. If ibus is however running in a different locale, I tried ja_JP.UTF-8, then the key an the Portuguese (Brazil) layout to the right of ‘P’ followed by ‘c’ inserts ć. In pt_BR.UTF-8 locale dead_acute + c = ç in ja_JP.UTF-8 locale dead_acute + c = ć and ibus does that nicely!