From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: Need better doc of compilation mode Date: Sun, 10 Sep 2006 17:10:03 -0700 Message-ID: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1157933461 19267 80.91.229.2 (11 Sep 2006 00:11:01 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 11 Sep 2006 00:11:01 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 11 02:11:01 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1GMZNw-0000K8-Gh for ged-emacs-devel@m.gmane.org; Mon, 11 Sep 2006 02:10:55 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GMZNu-0000VE-Hq for ged-emacs-devel@m.gmane.org; Sun, 10 Sep 2006 20:10:46 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GMZNj-0000V2-QM for emacs-devel@gnu.org; Sun, 10 Sep 2006 20:10:35 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GMZNb-0000P7-FV for emacs-devel@gnu.org; Sun, 10 Sep 2006 20:10:35 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GMZNb-0000P4-9K for emacs-devel@gnu.org; Sun, 10 Sep 2006 20:10:27 -0400 Original-Received: from [141.146.126.228] (helo=agminet01.oracle.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.52) id 1GMZOh-0005Or-P0 for emacs-devel@gnu.org; Sun, 10 Sep 2006 20:11:37 -0400 Original-Received: from rgmsgw02.us.oracle.com (rgmsgw02.us.oracle.com [138.1.186.52]) by agminet01.oracle.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k8B0ACiZ015429 for ; Sun, 10 Sep 2006 19:10:12 -0500 Original-Received: from dradamslap (dhcp-amer-csvpn-gw1-141-144-65-165.vpn.oracle.com [141.144.65.165]) by rgmsgw02.us.oracle.com (Switch-3.1.7/Switch-3.1.7) with SMTP id k8B0ABI7016576 for ; Sun, 10 Sep 2006 18:10:11 -0600 Original-To: "Emacs-Devel" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 Importance: Normal X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE 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:59646 Archived-At: 1. I just discovered this feature (yes, I think it's a feature) by accident: Click (mouse-2) a grep hit on the file name or line number, and the text that matches the regexp is highlighted in the source buffer. Click instead anywhere else on the grep hit and the whole line is highlighted in the source buffer. Nice. I see no documentation for this. The logical place to document it would be in the Compilation Mode node of the Emacs manual. 2. Node Compilation Mode says that the source hit is only momentarily highlighted. The word "momentarily" should be removed - that is just the default behavior. It also says "You can change the behavior of this highlighting with the variable `next-error-highlight'." It should instead say that that variable determines whether and for how long the hit is highlighted. 3. I filed a bug separately about the default highlight period (`next-error-highligt') being ridiculously short - it is 0.1 sec, so short I never even see the highlighting; it should be perhaps 10 or 30 seconds. I personally think the default value should be `t', which just moves the highlight each time you use `next-error'. 4. Node Grep Searching does not even say that what is said about `compilation-mode' in node Compilation Mode applies also to grep. It should say that buffer *grep* is in Grep mode, which has Compilation mode as a parent mode. More importantly, it should contain a link to node Compilation Mode, so readers can learn how to use Grep mode! We should never assume that users read the manual linearly, front to back. If a user goes to the manual looking for information on `grep', then s?he should be able to easily get to all pertinent information about it.