From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: Re: [21.1.90]: point put at point-min in *compilation* Date: Thu, 07 Feb 2008 14:52:31 -0500 Message-ID: References: <6EE216E1AA959543A555C60FF34FB76702CD2B19@maileube01.misys.global.ad> <6EE216E1AA959543A555C60FF34FB76702D254AF@maileube01.misys.global.ad> <86y79yrrdz.fsf@lola.quinscape.zz> <6EE216E1AA959543A555C60FF34FB76702DB6689@maileube01.misys.global.ad> Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: ger.gmane.org 1202414038 4972 80.91.229.12 (7 Feb 2008 19:53:58 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 7 Feb 2008 19:53:58 +0000 (UTC) Cc: emacs-pretest-bug@gnu.org, Simon.Marshall@misys.com To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 07 20:54:20 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JNCp1-0001Tm-CX for ged-emacs-devel@m.gmane.org; Thu, 07 Feb 2008 20:54:11 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JNCoY-0004AT-KF for ged-emacs-devel@m.gmane.org; Thu, 07 Feb 2008 14:53:42 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JNCnR-00037y-0w for emacs-devel@gnu.org; Thu, 07 Feb 2008 14:52:33 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JNCnQ-00037N-GI for emacs-devel@gnu.org; Thu, 07 Feb 2008 14:52:32 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JNCnQ-000374-5o for emacs-devel@gnu.org; Thu, 07 Feb 2008 14:52:32 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JNCnQ-0000p3-2L for emacs-devel@gnu.org; Thu, 07 Feb 2008 14:52:32 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.67) (envelope-from ) id 1JNCnP-0000uY-IK; Thu, 07 Feb 2008 14:52:31 -0500 In-reply-to: (message from Stefan Monnier on Wed, 06 Feb 2008 21:41:09 -0500) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:88452 gmane.emacs.pretest.bugs:20933 Archived-At: That would be a different feature, then. compilation-auto-jump-to-first-error only stops the scrolling as a side-effect. Its main effect is to do the equivalent of `next-error' when an error is spotted, so it really jumps to the source code where the first error was spotted. Indeed, that is not what I thought you meant. That seems too drastic to me. However, feature that would stop scrolling at the first error and leave point there, but would not go ahead and visit the source code on its own, might be a good third option for `compilation-scroll-output'.