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 07:00:40 +0300 Message-ID: <5691D768.3020908@yandex.ru> References: <83wprimto9.fsf@gnu.org> <56916C10.6050004@yandex.ru> <83oacumqmj.fsf@gnu.org> <56917246.1010800@yandex.ru> <5691795E.9010008@yandex.ru> <83lh7ym725.fsf@gnu.org> 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 1452398455 8822 80.91.229.3 (10 Jan 2016 04:00:55 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 10 Jan 2016 04:00:55 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 10 05:00:50 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 1aI7BR-0008Pj-RG for ged-emacs-devel@m.gmane.org; Sun, 10 Jan 2016 05:00:50 +0100 Original-Received: from localhost ([::1]:45130 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aI7BQ-0005QD-QE for ged-emacs-devel@m.gmane.org; Sat, 09 Jan 2016 23:00:48 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40121) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aI7BO-0005Q8-MU for emacs-devel@gnu.org; Sat, 09 Jan 2016 23:00:47 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aI7BL-0001lE-Hd for emacs-devel@gnu.org; Sat, 09 Jan 2016 23:00:46 -0500 Original-Received: from mail-lb0-x234.google.com ([2a00:1450:4010:c04::234]:34473) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aI7BL-0001l1-9R; Sat, 09 Jan 2016 23:00:43 -0500 Original-Received: by mail-lb0-x234.google.com with SMTP id cl12so22348013lbc.1; Sat, 09 Jan 2016 20:00:43 -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=4ItSDZ+tzGPDhXPN0Npub3r4hSKTA/Bk/ZktPDD+kP8=; b=0l3Tlrc7nXl5gLkegG5gsL+5WsBoJP/zj/pdLjQye6qsFoZB0E7mARNP6VzV554FuK Mk09WoiJU5Xpf1fAM7USM9UsZnAO4LjW45FHYGvjZ0l0Kcw2PMitAqswzmyvTQUWF6Mf 0gq/evVQECIu75JZK5YYwSm5PXRSEG5uapLDBGHdAgqHaLXcsP3hL9yXRR0AcBazkSsU W/DAyvYGV/3GXWRSTQ+1cofOX6+n8pyE7tLOlYtUawjGDpOdwBm+7JgPJcr7meB94vyI WfmsefpyzNoVAOWNhqq+sHuiLUuLqOxlsOgSfXreVcoUPwAPSyvdjTd5JrkfR23V2TVP 0MmQ== X-Received: by 10.112.202.66 with SMTP id kg2mr41876906lbc.50.1452398442244; Sat, 09 Jan 2016 20:00:42 -0800 (PST) Original-Received: from [192.168.1.190] ([178.252.127.222]) by smtp.googlemail.com with ESMTPSA id e130sm11514872lfe.9.2016.01.09.20.00.41 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 09 Jan 2016 20:00:41 -0800 (PST) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:43.0) Gecko/20100101 Thunderbird/43.0 In-Reply-To: <83lh7ym725.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2a00:1450:4010:c04::234 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:197947 Archived-At: On 01/10/2016 06:45 AM, Eli Zaretskii wrote: > tags-loop-continue is also used by Dired, see 'A' and 'Q' in > "Operating on Files". I'm fairly sure these commands are more obscure, and used considerably less frequently than find-tag, or xref-find-definitions that's poised to replace it. C-, is too nice a key binding to spend on them. If we want to retain some global binding for tags-loop-continue, let's move it to C-*. > Look at this from the user's POV: these two commands, as well as > tags-search and tags-query-replace, are still available, so users will > expect to be able to continue them as they did before. How can we > explain to them that the keybinding for that command changed? In the NEWS file, and in the manual? > Other than that, what technical solution is used to keep the command > and its keybinding available is unimportant, I think. It doesn't seem like tags-search uses any special keymap during its execution.