From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: History for query replace pairs Date: Mon, 06 Oct 2014 00:54:27 +0300 Organization: JURTA Message-ID: <87ppe6fai4.fsf@mail.jurta.org> References: <87a97ejxuo.fsf@mail.jurta.org> <87lhovik5c.fsf@lifelogs.com> <87mw9b8l0m.fsf@mail.jurta.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1412546495 25000 80.91.229.3 (5 Oct 2014 22:01:35 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 5 Oct 2014 22:01:35 +0000 (UTC) Cc: Emacs developers To: Yuri Khan Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 06 00:01:28 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 1Xatrr-0006NT-Pi for ged-emacs-devel@m.gmane.org; Mon, 06 Oct 2014 00:01:27 +0200 Original-Received: from localhost ([::1]:48810 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xatrr-00081O-FF for ged-emacs-devel@m.gmane.org; Sun, 05 Oct 2014 18:01:27 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40210) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xatri-00081I-VO for emacs-devel@gnu.org; Sun, 05 Oct 2014 18:01:25 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xatrc-00084M-PA for emacs-devel@gnu.org; Sun, 05 Oct 2014 18:01:18 -0400 Original-Received: from ps18281.dreamhost.com ([69.163.222.226]:59191 helo=ps18281.dreamhostps.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xatrc-000844-Io for emacs-devel@gnu.org; Sun, 05 Oct 2014 18:01:12 -0400 Original-Received: from localhost.jurta.org (ps18281.dreamhostps.com [69.163.222.226]) by ps18281.dreamhostps.com (Postfix) with ESMTP id 073DC30192BF81; Sun, 5 Oct 2014 15:01:10 -0700 (PDT) In-Reply-To: (Yuri Khan's message of "Sun, 5 Oct 2014 08:52:27 +0700") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (x86_64-pc-linux-gnu) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 69.163.222.226 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:174997 Archived-At: >> I realized right now that the most intuitive and convenient way is >> to implement a new general function to read two values in the minibuff= er >> with two entry fields. > > Where there is two, there is +infinity. Or more accurately: Where there is one, there is +infinity :) In case of the minibuffer, this means that we already have one entry field in the minibuffer, so it makes sense to extend it to multiple entry fields. > In other words, why stop at two? Let=E2=80=99s have a general function = that > accepts a description of zero or more parameters (I don=E2=80=99t know,= call > it a =E2=80=9Cdialog template=E2=80=9D or =E2=80=9Cinteractive specific= ation=E2=80=9D) and allows the > user to enter all of them using Customize-like widgets in the > minibuffer. (Though at this point it probably makes sense to maintain > both composite histories for each dialog and separate histories for > each field.) There are some problems with reading multiple values in the minibuffer like proposed by Josh. One problem is what a key to use to switch to another input field? In Customize-like widgets this is accomplished by TAB, but in the minibuffer TAB performs completion (not in query-replace but in completing-read generally). Customize provides another key M-TAB (M-C-i) for completion. We could use the same key for multi-value completing-read.