From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.bugs Subject: bug#46033: up arrow in query replace should not step into the prompt Date: Mon, 25 Jan 2021 19:14:52 +0200 Organization: LINKOV.NET Message-ID: <871re9x7jn.fsf@mail.linkov.net> References: <83czxx5b5j.fsf@gnu.org> <7sIywf2TKUTDST-QQJyKZzPIwKN6sUQuyb-1ReWQ09vPjrZwcAjSu-HOEwWJIAOio4ugVvqEYVcRFwMEJxN6rAitsq6Sf-dQkWQ67jHybfI=@protonmail.com> <87ft2rd1ot.fsf@mail.linkov.net> <877do3a4ed.fsf@mail.linkov.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40443"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (x86_64-pc-linux-gnu) Cc: "46033@debbugs.gnu.org" <46033@debbugs.gnu.org> To: reporter Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Jan 25 18:16:32 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 1l45Tb-000AOF-LC for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 25 Jan 2021 18:16:31 +0100 Original-Received: from localhost ([::1]:58774 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l45Ta-0008NA-MK for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 25 Jan 2021 12:16:30 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59506) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l45T8-0008Jh-Tf for bug-gnu-emacs@gnu.org; Mon, 25 Jan 2021 12:16:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:56493) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1l45T8-0008AD-2R for bug-gnu-emacs@gnu.org; Mon, 25 Jan 2021 12:16:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1l45T7-0001Xa-Ui for bug-gnu-emacs@gnu.org; Mon, 25 Jan 2021 12:16:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Juri Linkov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 25 Jan 2021 17:16:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 46033 X-GNU-PR-Package: emacs Original-Received: via spool by 46033-submit@debbugs.gnu.org id=B46033.16115949305875 (code B ref 46033); Mon, 25 Jan 2021 17:16:01 +0000 Original-Received: (at 46033) by debbugs.gnu.org; 25 Jan 2021 17:15:30 +0000 Original-Received: from localhost ([127.0.0.1]:39804 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1l45Sb-0001Wf-ON for submit@debbugs.gnu.org; Mon, 25 Jan 2021 12:15:30 -0500 Original-Received: from relay4-d.mail.gandi.net ([217.70.183.196]:53963) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1l45Sa-0001WO-2C; Mon, 25 Jan 2021 12:15:28 -0500 X-Originating-IP: 91.129.98.64 Original-Received: from mail.gandi.net (m91-129-98-64.cust.tele2.ee [91.129.98.64]) (Authenticated sender: juri@linkov.net) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id A01FFE0002; Mon, 25 Jan 2021 17:15:19 +0000 (UTC) In-Reply-To: (reporter's message of "Sat, 23 Jan 2021 18:53:02 +0000") 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:198575 Archived-At: tags 46033 fixed close 46033 28.0.50 thanks >> This is exactly what the patch does. Have you really tried it? > > Yes, I don't know what happened (I applied it manually), but I > must have made an error, because it didn't work. > > Then I checked the original code and I came up with the same > solution you did. > > So, yes, it does work. Thanks, and sorry for the confusion. Thanks for confirming, now this is fixed.