From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: is undefined Date: Sun, 23 Mar 2014 10:20:25 +0100 Organization: Organization?!? Message-ID: <87txapxodi.fsf@fencepost.gnu.org> References: <8761n5z54q.fsf@fencepost.gnu.org> <87y501xoj1.fsf@fencepost.gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1395566452 22741 80.91.229.3 (23 Mar 2014 09:20:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 23 Mar 2014 09:20:52 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Mar 23 10:21:00 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WReaR-00048V-U4 for ged-emacs-devel@m.gmane.org; Sun, 23 Mar 2014 10:21:00 +0100 Original-Received: from localhost ([::1]:59367 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WReaR-0005VG-H5 for ged-emacs-devel@m.gmane.org; Sun, 23 Mar 2014 05:20:59 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60050) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WReaD-0005FD-RJ for emacs-devel@gnu.org; Sun, 23 Mar 2014 05:20:51 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WRea8-0001eJ-07 for emacs-devel@gnu.org; Sun, 23 Mar 2014 05:20:45 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:41364) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WRea7-0001e3-Pz for emacs-devel@gnu.org; Sun, 23 Mar 2014 05:20:39 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WRea6-0003nQ-Ks for emacs-devel@gnu.org; Sun, 23 Mar 2014 10:20:38 +0100 Original-Received: from x2f422c0.dyn.telefonica.de ([2.244.34.192]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 23 Mar 2014 10:20:38 +0100 Original-Received: from dak by x2f422c0.dyn.telefonica.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 23 Mar 2014 10:20:38 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 40 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: x2f422c0.dyn.telefonica.de X-Face: 2FEFf>]>q>2iw=B6, xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN; i"; /yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:sgUl1UHP6V7KmFzGDVWauFxJSQw= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:170839 Archived-At: David Kastrup writes: > Andreas Schwab writes: > >> David Kastrup writes: >> >>> After upgrading to Ubuntu 14.04 (and using Cinnamon), I can no longer >>> use . Emacs flashes at me and displays " 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. > >> One workaround is to remove ibus, so compose is properly handled again >> by the X server. >> >> Nothing Emacs can do about. > > If this is nothing Emacs can do about, why is it working with > Gnome-terminal, Firefox, Gedit, the search box of Evince, even the GTK > file selector called from Emacs (when using the mouse in the File/Open > menu) and basically every other application on my system? > > Can you name a single _other_ application rather than Emacs that should > have a non-working Multi_key if "compose handling [was] broken on my > system"? > > If it is only Emacs showing that problem, shouldn't there be a > workaround even if you insist that Emacs is "correct" according to some > spec nobody else appears to be using? And even if we insist that all of this is "somebody else's problem", it won't go away by itself if it is only visible with Emacs and we don't bother getting to the bottom of it and reporting it to whoever else is somebody else. -- David Kastrup