From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Disable text conversion in map-ynp Date: Mon, 06 May 2024 17:56:02 +0300 Message-ID: <86le4nat19.fsf@gnu.org> References: <86pltzb0v0.fsf@gnu.org> <87pltz3y7b.fsf@yahoo.com> <86o79jawhp.fsf@gnu.org> <87h6fb3u4b.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2170"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon May 06 16:56:57 2024 Return-path: Envelope-to: ged-emacs-devel@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 1s3zlw-0000Ot-R1 for ged-emacs-devel@m.gmane-mx.org; Mon, 06 May 2024 16:56:57 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1s3zlM-0001Zg-Ux; Mon, 06 May 2024 10:56:20 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s3zlL-0001ZF-2y for emacs-devel@gnu.org; Mon, 06 May 2024 10:56:19 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s3zlK-0006IZ-9o; Mon, 06 May 2024 10:56:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=KBtmGTkKTUBmChiqf7MpmzlW5TheVU/VL+UuDiMx8RQ=; b=FZbHZXCgmJDr wZNvjx/93/hOJ3/YkzazCt8y+R871fxMTmVPaLpTUKB5AEN9uvH+110hUQeN8L/E4w0HGROUfzw9k fJKqZXRqXkUNueLtRBoma8EhznUyYGOnzSobhz5DaTqPF46/2AFHNqiTI9Jesrp2mgXM1quy2UfzK 3LQC7mFAPlzkWf7HRdjrsomyv5OoErv3zBdYkkIkuFBjuyqvA+s89ktTbS7sgb43KdQkN0Usi6ZYC CbORGxBQld37C21YD0SjCiIl0kKd8YSRVrrYDdI69k1+0OQpb/P+3QDj+oLtHz22oO1r3CfQw+lS0 DmBXgxksXI4Ro49MVxQoMg==; In-Reply-To: <87h6fb3u4b.fsf@yahoo.com> (message from Po Lu on Mon, 06 May 2024 22:14:28 +0800) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:318900 Archived-At: > From: Po Lu > Cc: emacs-devel@gnu.org > Date: Mon, 06 May 2024 22:14:28 +0800 > > > and if so, is there a way to suppress input methods on Android while > > still calling read-event? > > There could be, but it would entail calling read-char rather than > read-event, or introducing a new parameter to read-event. Don't we have some variable that could be bound around the call to read-event to suppress text-conversion? If not, we should, because this is definitely not the last situation where it could get in the way. > > IOW, I'd like to keep using read-event, but make sure text-conversion > > doesn't happen, instead of switching to read-key. And if that's > > impossible for some reason, how about using read-key only on Android? > > I think an informed conclusion would be easier to draw if you directed > me to previous occasions where issues arose from switching from read-key > to read-event in similar contexts. I don't have it ready. But I'm not sure how would that help. If you look at what read-key does and compare that to read-event, you will see that the differences are so significant as to thwart any attempt to figure out when and how these two will behave differently. But okay, see these: bug#24635 bug#29150 https://lists.gnu.org/archive/html/emacs-devel/2020-11/msg00601.html