From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: tags-loop-continue Date: Sun, 10 Jan 2016 00:19:26 +0300 Message-ID: <5691795E.9010008@yandex.ru> References: <83wprimto9.fsf@gnu.org> <56916C10.6050004@yandex.ru> <83oacumqmj.fsf@gnu.org> <56917246.1010800@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1452374380 32121 80.91.229.3 (9 Jan 2016 21:19:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 9 Jan 2016 21:19:40 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 09 22:19:40 2016 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 1aI0vB-0002UK-1i for ged-emacs-devel@m.gmane.org; Sat, 09 Jan 2016 22:19:37 +0100 Original-Received: from localhost ([::1]:43114 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aI0vA-0004UY-9m for ged-emacs-devel@m.gmane.org; Sat, 09 Jan 2016 16:19:36 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57661) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aI0v6-0004Rz-7d for emacs-devel@gnu.org; Sat, 09 Jan 2016 16:19:32 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aI0v2-0001SH-U8 for emacs-devel@gnu.org; Sat, 09 Jan 2016 16:19:32 -0500 Original-Received: from mail-lb0-x236.google.com ([2a00:1450:4010:c04::236]:35981) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aI0v2-0001SB-MR; Sat, 09 Jan 2016 16:19:28 -0500 Original-Received: by mail-lb0-x236.google.com with SMTP id oh2so238220082lbb.3; Sat, 09 Jan 2016 13:19:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=9qFpZr3uXz4luDzmd6c7Pl+2iAE3mPIGYJN+Ndl4VhM=; b=UUzz5oRoo4p9cRp5+vMCv/sbWb4E9g4eiO14qkRTeFTJ+zDO1OHJ4ZfSWVnbwSshf+ YrDbpSARp+mTdsd7pm17nDE1FsGmX/d3p6DXVsnRKWliFOcCxmnzfSSXW94xp12REE+T aeGuHVEmihH7Fmt9xEVTQ6pm7CMx18GEHJWCicqdWG5F38SeodcDueG++qZ/hkL/ko+/ 4QnnitFUjuBZ3Pe3Ejt312etz9ayCh54LkRqMMZ8JrYQW98HG6KMCTsw4ptRQOk+eo7s yALSIpgKzisNlDJGEVBipUguhsGZr9i0hrp8dHmKE2Oi5u9WK3h/NO8kNyNCESPyccSd e2Zg== X-Received: by 10.112.160.232 with SMTP id xn8mr7508874lbb.22.1452374368050; Sat, 09 Jan 2016 13:19:28 -0800 (PST) Original-Received: from [192.168.1.190] ([178.252.127.222]) by smtp.googlemail.com with ESMTPSA id k3sm10000361lbp.9.2016.01.09.13.19.26 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 09 Jan 2016 13:19:26 -0800 (PST) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:43.0) Gecko/20100101 Thunderbird/43.0 In-Reply-To: <56917246.1010800@yandex.ru> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2a00:1450:4010:c04::236 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:197937 Archived-At: On 01/09/2016 11:49 PM, Dmitry Gutov wrote: > If it's only supposed to be used in tags-query-replace and > tags-query-replace now, why does it need a binding? It only seems to be > used in a non-interactive way. Or if we *are* supposed to invoke tags-loop-continue interactively when using these commands, can't we make sure that it's only bound *then*? Like, set that binding in certain major modes' key maps? Or, if that's not an option, temporarily enter a minor mode that would set that binding? IIUC, tags-query-replace *does* use certain keymaps for its whole duration. And regarding tags-search, it shouldn't be too hard to implement an alternative that would use an xref buffer for output. If you like that idea, what shall we call it?