From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings Newsgroups: gmane.emacs.bugs Subject: bug#48042: 26.3; Macros don't work with french-postfix input method Date: Fri, 14 May 2021 17:07:41 +0000 Message-ID: <425cd7715b770b248347@heytings.org> References: <86pmyghqf1.fsf@upmc.fr> <425cd7715bc9fae8b39a@heytings.org> <831ra9zi4x.fsf@gnu.org> <425cd7715bda5353110e@heytings.org> <83y2chxvg4.fsf@gnu.org> <425cd7715b4c15a15813@heytings.org> <83v97lxu0f.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22339"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 48042@debbugs.gnu.org, harven@free.fr To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri May 14 19:44:33 2021 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 1lhbrU-0005d4-W2 for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 14 May 2021 19:44:33 +0200 Original-Received: from localhost ([::1]:49170 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lhbrU-0005rO-1R for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 14 May 2021 13:44:32 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33444) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lhbIA-0004l8-IF for bug-gnu-emacs@gnu.org; Fri, 14 May 2021 13:08:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:35411) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lhbIA-0006XD-9Q for bug-gnu-emacs@gnu.org; Fri, 14 May 2021 13:08:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lhbIA-0005nX-3A for bug-gnu-emacs@gnu.org; Fri, 14 May 2021 13:08:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 14 May 2021 17:08:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 48042 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: confirmed Original-Received: via spool by 48042-submit@debbugs.gnu.org id=B48042.162101206622262 (code B ref 48042); Fri, 14 May 2021 17:08:02 +0000 Original-Received: (at 48042) by debbugs.gnu.org; 14 May 2021 17:07:46 +0000 Original-Received: from localhost ([127.0.0.1]:46957 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lhbHu-0005n0-3s for submit@debbugs.gnu.org; Fri, 14 May 2021 13:07:46 -0400 Original-Received: from heytings.org ([95.142.160.155]:50940) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lhbHq-0005mq-V6 for 48042@debbugs.gnu.org; Fri, 14 May 2021 13:07:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20210101; t=1621012061; bh=iUOBtefobqnNg1oaFwzR3/t6AyI0QTg9jmuwu9JawDc=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=kpD+hjfXTPr+WtI08nlqrTv6LprFmqMATiq/fsxLs1iQ2Rak8G6JTG514Cvh6VCj1 cxssuL4agcpuvHSukLYQyETkzsZ6EytW+mINfdsXoXYXJsvlPraH6+pUqYXklGe7Ep h+z4SmayKhWgJFkEXz1WqwqY9YHtPTJfMQI1+wCkXCpyPA1hkGGVaLRnKO/OQ1Zmbh mdd7GaF9Esikxg1UChpgfBytM9vUEannwLezKXbha8zkbi+np/MpZPE7dzkkt37R7g CPJFqXOWTPNSNvmni1YyI79zLrw8vBMPOQGY/j16sY/A1vWfGl/Rt6NIfg7Oy1V3Vh OTFN0DGinTKkQ== In-Reply-To: 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:206545 Archived-At: >> If you are asking how I'd like to proceed with this bug, then, as I >> wrote in another message, I'd like us to have a full understanding of >> why binding inhibit--record-char didn't work well enough in the case in >> point. It did solve some of the problem we had before that change, but >> didn't solve all of it -- why? > > BTW, another possible way to attack the problem is to arrange for the > code that pushes to `unread-command-events` to use events of the form > `(t . EVENT)` so as to tell explicitly that we don't want them recorded. > I guess you mean '(no-record . EVENT)'? The docstring indicates that '(t . EVENT)' means that EVENT is added to 'this-command-keys'.