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: Thu, 14 Jan 2016 22:15:21 +0300 Message-ID: <5697F3C9.5040702@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> <5691D768.3020908@yandex.ru> <83bn8tmnvq.fsf@gnu.org> <56928356.2000609@yandex.ru> <8360z1mkfc.fsf@gnu.org> <5696EE9D.2090708@yandex.ru> <838u3si22k.fsf@gnu.org> <5697C7A8.6060601@yandex.ru> <83wprcgjxk.fsf@gnu.org> <5697DA3B.3070706@yandex.ru> <83io2wggh8.fsf@gnu.org> <5697EC73.6040302@yandex.ru> <83fuy0gf2j.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 1452798951 24908 80.91.229.3 (14 Jan 2016 19:15:51 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 14 Jan 2016 19:15:51 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 14 20:15:43 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 1aJnN1-000630-0O for ged-emacs-devel@m.gmane.org; Thu, 14 Jan 2016 20:15:43 +0100 Original-Received: from localhost ([::1]:44280 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aJnN0-0000EQ-B5 for ged-emacs-devel@m.gmane.org; Thu, 14 Jan 2016 14:15:42 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38418) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aJnMn-0000EG-60 for emacs-devel@gnu.org; Thu, 14 Jan 2016 14:15:30 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aJnMi-0001MZ-Td for emacs-devel@gnu.org; Thu, 14 Jan 2016 14:15:29 -0500 Original-Received: from mail-lb0-x22c.google.com ([2a00:1450:4010:c04::22c]:35538) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aJnMi-0001MU-Ko; Thu, 14 Jan 2016 14:15:24 -0500 Original-Received: by mail-lb0-x22c.google.com with SMTP id bc4so302203140lbc.2; Thu, 14 Jan 2016 11:15:24 -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=LX9OWDmCzTKeXPSEgtZJRTMqE3XzZzYIwkb/eixHxcA=; b=NAyuZI+BPcFUbBTEuy19CQgeqAgmKmVNFswBTm0F/fvzp7tRwB1uw1a72Gg0zyOUWi EI3nS2LZJe8fPBmhLsyV7xcS5KYyDb/8LcuR+zbKhK6o/Dg6p/TImPRATxC1sB3z4eWR F+fM78MI8il3egGlvBBbLzKp8zdKFWxkcpWXgCI8Aee3lSOy5+lpK9OrJYWA4jrzkRSx MpJzfGgzf+XbhB0QAsXbjQoIZiUnUK6VXtAj2bkqu//WSObHzHIeJYHnOK/rfbN2r1kx aEOMrcLUI1y13TOp7NGUKLA2L7uBypj7Io6VMqemzgwATWqUmhGF9J6JVa8ViSem8tEE D+ZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:to:references:cc:from:message-id :date:user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=LX9OWDmCzTKeXPSEgtZJRTMqE3XzZzYIwkb/eixHxcA=; b=WC8Yoyj65dRccM/b0Gb59K9JcANVNW7m8lHXaFj54NxiJR5sqa4xbEkgA0HOHIxHnk Vgsx6Se16xVK7kv0rm2+LsSMRzEBQykY2ogLbFegRxWeJGPQqkqfnCJCP/GmA28T5c/U FFUQpwSF8k17d19ubZvmJt5CI/sqyDOHaJN/T2XWnSn53z933LtSm5OH4m6ZtWcBTVc/ FLzKjIbEfeU4P4n2jq1+uQ1ydnq4q8gRNnXYnTQXpTyXgIzLyHsx0PMrAbFeAUJTDGkc 9TB6/ArNEvd4zbluCN/UhwBx0lOMxsty8Nm6d3kwJW+9/7iWZzMxtxc6Rd8TgdGajbmd RQGg== X-Gm-Message-State: ALoCoQl0zex7ZrmBVbwW8uk41m4spLTDTolMzvh4knGoQhh/tbKVnFXOA/V79XqStJs3tp+k5349QJiENXQnYg0Xr+hhU7GvmQ== X-Received: by 10.112.64.5 with SMTP id k5mr1570768lbs.133.1452798923509; Thu, 14 Jan 2016 11:15:23 -0800 (PST) Original-Received: from [192.168.1.190] ([178.252.127.222]) by smtp.googlemail.com with ESMTPSA id a124sm941165lfa.40.2016.01.14.11.15.22 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 14 Jan 2016 11:15:22 -0800 (PST) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:43.0) Gecko/20100101 Thunderbird/43.0 In-Reply-To: <83fuy0gf2j.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::22c 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:198152 Archived-At: On 01/14/2016 10:02 PM, Eli Zaretskii wrote: > I just want the people who are used to 'Q' to have something similar > to what they knew before. It might be okay to show *xref*-style > buffer with the hits, though. Then they can call `next-error' instead. Unfortunately, this facility is unreliable in the presence of different next-error-function's in target buffers. But that was before xref came along. > Is that what you meant by "press 'r'"? I just mean that we don't have to have a separate command outside of search results buffer. Yes, it's unfamiliar, but the functionality is covered, and the manual will tell the user needs to do. `r', pressed in an project-find-regexp output buffer, will call xref-query-replace. Which, yes, is currently implemented using `perform-replace', but that should change. > Why is it so important to use that particular binding for > xref-pop-marker-stack? What's wrong with 'M-*'? SLIME has shown that it's better. M-* is much farther from M-., and you can't as quickly navigate back by keeping M pressed, releasing `.' and pressing `,'. And really, the xref UI doesn't need it. We should commit to one default paradigm of behavior. (If we had customizable switching between the old and the new UIs, we'd introduce a minor mode that would also change the global bindings). >> - Do we create versions of all new commands that use the traditional >> interface? > > No, not necessarily. They should be functionally equivalent and > similar enough in principle. They don't have to have the same > interface. What are the requirements, then? > For lack of a better name, I guess. The old one was called "etags" > for the same reason, and had the same problems. Yes, ugh. But now we have two different UIs, so the issue is more pressing, unless we're content on altogether migrating off the old UI. > You will still have the problem of coming up with a suitable name ;-) Also yes.