From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?=C5=A0t=C4=9Bp=C3=A1n_?= =?UTF-8?Q?N=C4=9Bmec?= Newsgroups: gmane.emacs.bugs Subject: bug#53698: 29.0.50; ibus input method of chinese with rime engine can't work in v27 and ibus candidate menu blink in v29 Date: Thu, 03 Feb 2022 13:49:52 +0100 Message-ID: <20220203134952+0100.120834-stepnem@gmail.com> References: <87ee4k924n.fsf@yahoo.com> <20220203123202+0100.45147-stepnem@gmail.com> <87tudg5f4a.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24143"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: 53698@debbugs.gnu.org, =?UTF-8?Q?=E6=B1=9F_?= =?UTF-8?Q?=E6=9A=87=E7=96=86?= To: Po Lu Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Feb 03 13:52:43 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nFbbP-000650-6J for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 03 Feb 2022 13:52:43 +0100 Original-Received: from localhost ([::1]:59400 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nFbbN-0005HH-LX for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 03 Feb 2022 07:52:41 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:33848) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nFbYq-0005BM-6o for bug-gnu-emacs@gnu.org; Thu, 03 Feb 2022 07:50:10 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:60858) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nFbYo-0005wg-IM for bug-gnu-emacs@gnu.org; Thu, 03 Feb 2022 07:50:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nFbYo-0000Vv-EQ for bug-gnu-emacs@gnu.org; Thu, 03 Feb 2022 07:50:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?=C5=A0t=C4=9Bp=C3=A1n_?= =?UTF-8?Q?N=C4=9Bmec?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 03 Feb 2022 12:50:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 53698 X-GNU-PR-Package: emacs Original-Received: via spool by 53698-submit@debbugs.gnu.org id=B53698.16438925951956 (code B ref 53698); Thu, 03 Feb 2022 12:50:02 +0000 Original-Received: (at 53698) by debbugs.gnu.org; 3 Feb 2022 12:49:55 +0000 Original-Received: from localhost ([127.0.0.1]:54755 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nFbYg-0000VU-NW for submit@debbugs.gnu.org; Thu, 03 Feb 2022 07:49:55 -0500 Original-Received: from mail-ed1-f43.google.com ([209.85.208.43]:34681) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nFbYe-0000VC-6k for 53698@debbugs.gnu.org; Thu, 03 Feb 2022 07:49:53 -0500 Original-Received: by mail-ed1-f43.google.com with SMTP id w20so1822902edc.1 for <53698@debbugs.gnu.org>; Thu, 03 Feb 2022 04:49:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:in-reply-to:references:user-agent:date :message-id:mime-version:content-transfer-encoding; bh=DqG9JSf1XQeYUPdtTF4LAlyDxuJOD5hXiD4ChYZRZhQ=; b=KU6eN94Zn+CB7Qopi8VopagbZwB/Cyn4+GwSLwkQSkdPpSzeriCPFY3b+fxS4E3jdo rorq92186K6sKnq+29sRUvnfT163fOWGzSYNVUsIbbtf/pp2UwnOHkVp3GYadL7dXmg7 kL2SuzvcUUZU6FxvqrftmPrq1qOJ+hOM7RfSkA/UnRsxyXmJPGTGAA3Jgpidcc6nUfsl 1Lp9WhBmQZJjih/vXpF/FaDKCywJooF1CdN+5JvBbBgl2Pad00DloHQ6JhnJOAK4q7LS eUp9wP9jSjRgnDRQXOHGcb7BO9VI5rhdAJWvaP5/y181ZexowvzKWoyuKDpcQ6cftJc8 LAow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references :user-agent:date:message-id:mime-version:content-transfer-encoding; bh=DqG9JSf1XQeYUPdtTF4LAlyDxuJOD5hXiD4ChYZRZhQ=; b=QBtOeEm0g+Ws8yflQ8kdMA1SRgOnW3LnnvwmHjpN/VdEkwWYveanYeQ0he5DV9CHcY 3OodDjSGnex3PTl3pPHviHL0+2H+yzJHl7k2Q0YvWsrlvnjEK0/5MGNFi/wL0pw126Ga TH30YyWlK/OVnbKEPnmqMu1A+3euZr3cZlP1wZnrl9/dWeBQYIib8qIvSBg2u/A3JpnX bjZZIOwZqZB2A3oC/n40tgzJaEWN3Hv2xlqUV/5WMvpnyXAyx7nSjfmUjmr5ONRHb70G qGxq7+19nDGpoFcG/jOh91banbuTXja+gDC11ktoeWS1NGQpYfs4eTjcbBzD3bkdUso1 y5Sw== X-Gm-Message-State: AOAM531OixVXidP1tHC75CcS9pUXXjETDr5j4F6r2k6YxPI7jqeVSfC8 iFAHHMDkx5QdXHl0Z4n2Ehg= X-Google-Smtp-Source: ABdhPJwPiCbduVkNp5FLqj8znzYQqEYvDxBaiSgf+K5Zn6pc9lPrRNPGkpB77Iv4xCO4ikUDrV7qkw== X-Received: by 2002:a50:a454:: with SMTP id v20mr35080568edb.176.1643892586065; Thu, 03 Feb 2022 04:49:46 -0800 (PST) Original-Received: from localhost ([185.112.167.34]) by smtp.gmail.com with ESMTPSA id d22sm8692776ejr.138.2022.02.03.04.49.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 03 Feb 2022 04:49:45 -0800 (PST) In-Reply-To: <87tudg5f4a.fsf@yahoo.com> (Po Lu via's message of "Thu, 03 Feb 2022 20:06:13 +0800") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:225880 Archived-At: On Thu, 03 Feb 2022 20:06:13 +0800 Po Lu via wrote: > =C5=A0t=C4=9Bp=C3=A1n N=C4=9Bmec writes: > >> The problem with that option is that it apparently breaks some key >> modifiers, e.g. with x-gtk-use-native-input non-nil it becomes >> impossible to bind C-S-u (Emacs processes it the same as C-u). > > Yes, the problem is the same as on the PGTK port, since both use the > same input method system. > >> AFAICT, X input has been broken (or rather, you get to pick: either you >> get working IME (with x-gtk-use-native-input non-nil), or working >> modifier keybindings (with it being nil); but given that >> x-gtk-use-native-input defaults to nil, for many/most people IME will >> just stop working; > > It works here for me (Fedora 35, stock GNOME with IBus), but we do want > to fix this problem and keep X input methods working as well as they > used to. I don't use any desktop environment, just plain X.Org (with XMonad on Arch Linux). > Do you see the same problem in other programs that use XIM, such as > xterm? No, it continues working everywhere as before (including xterm), with the exception of Emacs. > If not, try placing: > > Emacs.inputStyle: none > in your X defaults file, and see if that solves the problem. It does not (no observable effect). > Most of this is caused by a more fundamental problem: XIM is an obsolete > interface with many limitations; most applications today rely on the > authors of input method frameworks to provide input modules for their > specific toolkit, and as a result the XIM backends for input method > frameworks get very little testing and are buggy. > > Unfortunately, since we cannot demand that input method frame developers > provide modules specifically for supporting Emacs, the only choice we > have is between using the legacy interface standard to X (XIM) or the > toolkit's input method system (GTK native input), each with its own > limitations and advantages. > > It's a sad situation, but there's nothing we can do. > >> also, it's not just IMEs like fcitx or ibus, XkbLayout switching has >> the same problem) since the commit that introduced the option >> (bisected yesterday): >> >> commit d76fb0c11e98 >> Author: Po Lu >> Date: Sat Jan 8 15:21:51 2022 +0800 >> >> Allow using GTK+ to handle input methods on X > > Are you sure that's the commit which introduced this bug, and not one of > the preceeding commits that added features to the XIM support? Yes. My git-bisect(1) invocation was git bisect start 3dfefb8bb4d9 041fff3d3dda and given the interactive nature of the issue, I watched IME/XkbLayout switching break and work again repeatedly while jumping around the commit. The preceding 63c83e4 does not exhibit the issues. > I find that hard to believe, since it doesn't touch anything related to > XIM. --=20 =C5=A0t=C4=9Bp=C3=A1n