From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tom Newsgroups: gmane.emacs.help Subject: Re: Seeing which commits modified a range of lines? Date: Thu, 6 Nov 2014 20:56:21 +0000 (UTC) Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1415307422 13655 80.91.229.3 (6 Nov 2014 20:57:02 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 6 Nov 2014 20:57:02 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Nov 06 21:56:56 2014 Return-path: Envelope-to: geh-help-gnu-emacs@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 1XmU6x-0008Vz-HX for geh-help-gnu-emacs@m.gmane.org; Thu, 06 Nov 2014 21:56:55 +0100 Original-Received: from localhost ([::1]:56024 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XmU6x-0005HN-8O for geh-help-gnu-emacs@m.gmane.org; Thu, 06 Nov 2014 15:56:55 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53406) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XmU6i-0005GO-DY for help-gnu-emacs@gnu.org; Thu, 06 Nov 2014 15:56:46 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XmU6c-0008FR-G2 for help-gnu-emacs@gnu.org; Thu, 06 Nov 2014 15:56:40 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:42874) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XmU6c-0008FM-Ah for help-gnu-emacs@gnu.org; Thu, 06 Nov 2014 15:56:34 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XmU6b-00089u-C2 for help-gnu-emacs@gnu.org; Thu, 06 Nov 2014 21:56:33 +0100 Original-Received: from 94-21-240-142.pool.digikabel.hu ([94.21.240.142]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 06 Nov 2014 21:56:33 +0100 Original-Received: from adatgyujto by 94-21-240-142.pool.digikabel.hu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 06 Nov 2014 21:56:33 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 23 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 94.21.240.142 (Mozilla/5.0 (Windows NT 6.1; rv:33.0) Gecko/20100101 Firefox/33.0) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:100803 Archived-At: Stefan Monnier iro.umontreal.ca> writes: > For most backends, such a loop will take forever to terminate The termination problem could be mitigated by introducing a limit for the search. For example, after going back, say, 10 revisions (or if it's a time limit then after working for, say, 5 seconds) the loop stops and emacs asks the user if it should continue working or the user wants to see the results up to that point. If the latter then the user can peruse the results and if more info is needed then he can restart the search which picks up where it left off using the previously collected info and continues working until the limit is reached again, etc. Usually the user looks for some specific change impacting that code chunk, so there is no need to go back to the beginning of time. If the user can control the process the above described way then he goes back only as far as needed, so the termination problem may be less of an issue.