From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: History for query replace pairs Date: Tue, 21 Oct 2014 14:23:04 -0400 Message-ID: References: <87a97ejxuo.fsf@mail.jurta.org> <87lhovik5c.fsf@lifelogs.com> <87wq8egh3r.fsf@lifelogs.com> <87ppe4zv0t.fsf@mail.jurta.org> <87k34ba5sn.fsf@mail.jurta.org> <87siiq4gpv.fsf@mail.jurta.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1413915822 30458 80.91.229.3 (21 Oct 2014 18:23:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 21 Oct 2014 18:23:42 +0000 (UTC) Cc: emacs-devel@gnu.org To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 21 20:23:35 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 1Xge5n-0006Ts-FL for ged-emacs-devel@m.gmane.org; Tue, 21 Oct 2014 20:23:35 +0200 Original-Received: from localhost ([::1]:52923 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xge5m-0004AB-Gx for ged-emacs-devel@m.gmane.org; Tue, 21 Oct 2014 14:23:34 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37013) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xge5S-000495-58 for emacs-devel@gnu.org; Tue, 21 Oct 2014 14:23:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xge5J-00088f-MD for emacs-devel@gnu.org; Tue, 21 Oct 2014 14:23:14 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:17109) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xge5J-00088Z-Hu for emacs-devel@gnu.org; Tue, 21 Oct 2014 14:23:05 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArUGAIDvNVNFpY87/2dsb2JhbABZgwaDSsA9gRcXdIIlAQEBAQIBViMFCws0EhQYDSSIBAjSGReOegeEOASpGYFqg0wh X-IPAS-Result: ArUGAIDvNVNFpY87/2dsb2JhbABZgwaDSsA9gRcXdIIlAQEBAQIBViMFCws0EhQYDSSIBAjSGReOegeEOASpGYFqg0wh X-IronPort-AV: E=Sophos;i="4.97,753,1389762000"; d="scan'208";a="94757487" Original-Received: from 69-165-143-59.dsl.teksavvy.com (HELO pastel.home) ([69.165.143.59]) by ironport2-out.teksavvy.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 21 Oct 2014 14:23:04 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 9C2064820; Tue, 21 Oct 2014 14:23:04 -0400 (EDT) In-Reply-To: <87siiq4gpv.fsf@mail.jurta.org> (Juri Linkov's message of "Tue, 14 Oct 2014 22:02:52 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.181 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:175660 Archived-At: > But the main question in both cases which key to use to browse FROM-TO pairs > from the minibuffer's history? It seems both M-p and should still get > either FROM or TO from the history one by one, so it would be easy to reuse > a previous TO for the FROM part (to invert replacements). What about ? The only thing that makes sense is to get the pairs via M-p/M-n and up/down. Of course, that clashes with the current behavior and hence prevents access to "TO-history" in the FROM case and to "FROM-history" in the TO case. But if we only do that for the FROM prompt (which is already a "FROM or FROM/TO pair" because of the behavior in case you just hit RET, and would turn even more clearly into a "FROM or FROM/TO pair"), I don't think it's that bad: - You still have access to the "TO-history" in the FROM case, indirectly (by browsing the corresponding FROM/TO pair and erasing the FROM and the separator). - You still have access to the FROM-history in the TO case, just as before. Stefan