unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>, emacs-devel@gnu.org
Subject: Re: <Multi_key> is undefined
Date: Sun, 23 Mar 2014 10:29:12 +0100	[thread overview]
Message-ID: <874n2pl0uv.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 532EA750.5060903@dancol.org

Daniel Colascione <dancol@dancol.org> writes:

> On 03/23/2014 02:17 AM, David Kastrup wrote:
>> Andreas Schwab <schwab@linux-m68k.org> writes:
>> 
>>> David Kastrup <dak@gnu.org> writes:
>>>
>>>> After upgrading to Ubuntu 14.04 (and using Cinnamon), I can no longer
>>>> use <Multi_key>.  Emacs flashes at me and displays "<Multi_key> is
>>>> undefined".
>>>
>>> That means compose handling is broken on your system.
>> 
>> It's likely not just "my system" but in a month of time the most widely
>> deployed GNU/Linux system.
>
> FWIW, it's broken on 13.10 for me too.

Interesting.  Possibly my use of Cinnamon put me behind the time.

> Nulling out XMODIFIERS fixes it for me; that environment variable
> normally contains something about ibus; making that change ourselves
> probably breaks other functionality though.

dak@lola:/usr/local/tmp/emacs-build$ echo $XMODIFIERS 
@im=ibus

Huh.

Starting Emacs from the command line, I get
emacs

** (emacs:14442): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-hJwGKKvPZH: Connection refused

There is nothing remotely like that file.  However, that seems to be a
red herring regarding _this_ problem since with

XMODIFIERS="" emacs

I get the same error message (including the same file name), but indeed
the compose character starts working.

-- 
David Kastrup



  reply	other threads:[~2014-03-23  9:29 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-23  8:33 <Multi_key> is undefined David Kastrup
2014-03-23  8:48 ` Andreas Schwab
2014-03-23  9:17   ` David Kastrup
2014-03-23  9:20     ` Daniel Colascione
2014-03-23  9:29       ` David Kastrup [this message]
2014-03-23 16:14         ` Eli Zaretskii
2014-03-23 16:22           ` David Kastrup
2014-03-23 16:47             ` Eli Zaretskii
2014-03-23 17:50             ` Werner LEMBERG
2014-03-23 18:15               ` David Kastrup
2014-03-23 10:21       ` Eric Abrahamsen
2014-03-23 13:20         ` David Kastrup
2014-03-23  9:20     ` David Kastrup
2014-03-23  9:40     ` Andreas Schwab
2014-03-23  9:52       ` David Kastrup
2014-03-23  9:56         ` Andreas Schwab
2014-03-23 10:08           ` Daniel Colascione
2014-03-23 10:16             ` Daniel Colascione
2014-03-23 10:23               ` Werner LEMBERG
2014-03-23 10:25               ` Daniel Colascione
2014-03-23 11:37                 ` Werner LEMBERG
2014-03-23 11:39                   ` Daniel Colascione
2014-03-23 11:44                     ` Werner LEMBERG
2014-03-23 11:50                       ` Daniel Colascione
2014-03-23 11:57                         ` Werner LEMBERG
2014-03-23 12:10                           ` Daniel Colascione
2014-03-23 14:33                             ` Barry Fishman
2014-03-23 14:46                               ` Daniel Colascione
2014-03-23 19:36                                 ` Barry Fishman
2014-03-24  1:40                                   ` Stephen J. Turnbull
2014-03-23 13:44                 ` David Kastrup
2014-03-23 10:16 ` Werner LEMBERG
2014-03-23 13:55   ` Barry Fishman
2014-03-23 12:35 ` Teemu Likonen

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=874n2pl0uv.fsf@fencepost.gnu.org \
    --to=dak@gnu.org \
    --cc=dancol@dancol.org \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@linux-m68k.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).