From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: compilation-highlight-duration Date: Tue, 4 May 2004 13:32:44 -0700 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1083703854 8689 80.91.224.253 (4 May 2004 20:50:54 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 4 May 2004 20:50:54 +0000 (UTC) Cc: Tak Ota , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Tue May 04 22:50:44 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BL6sG-0006n8-00 for ; Tue, 04 May 2004 22:50:44 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BL6sG-0001ch-00 for ; Tue, 04 May 2004 22:50:44 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1BL6rQ-0007Oy-N9 for emacs-devel@quimby.gnus.org; Tue, 04 May 2004 16:49:52 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1BL6jL-0003pl-Ou for emacs-devel@gnu.org; Tue, 04 May 2004 16:41:31 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1BL6il-0003fB-Jy for emacs-devel@gnu.org; Tue, 04 May 2004 16:41:28 -0400 Original-Received: from [148.87.2.204] (helo=inet-mail4.oracle.com) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.30) id 1BL6cH-0000QM-Cj; Tue, 04 May 2004 16:34:13 -0400 Original-Received: from inet-mail4.oracle.com (localhost [127.0.0.1]) by inet-mail4.oracle.com (Switch-3.1.4/Switch-3.1.0) with ESMTP id i44KUIMw016152; Tue, 4 May 2004 13:30:18 -0700 (PDT) Original-Received: from rgmgw3.us.oracle.com (rgmgw3.us.oracle.com [138.1.191.12]) by inet-mail4.oracle.com (Switch-3.1.4/Switch-3.1.0) with ESMTP id i44KUFPv016103; Tue, 4 May 2004 13:30:15 -0700 (PDT) Original-Received: from rgmgw3.us.oracle.com (localhost [127.0.0.1]) by rgmgw3.us.oracle.com (Switch-3.1.4/Switch-3.1.0) with ESMTP id i44KWkYs021454; Tue, 4 May 2004 14:32:46 -0600 Original-Received: from dradamslap (dhcp-amer-vpn-gw2-east-141-144-66-185.vpn.oracle.com [141.144.66.185]) by rgmgw3.us.oracle.com (Switch-3.1.4/Switch-3.1.0) with SMTP id i44KWjea021431; Tue, 4 May 2004 14:32:46 -0600 Original-To: "Kim F. Storm" , "Juri Linkov" , X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Importance: Normal X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:22750 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:22750 Juri Linkov writes: > > Another good indication method is persistent (i.e. non-flashing!) > > overlays highlighted with a special face on matching lines in > > compilation output buffer and source code buffer. > > IMO it would be a lot more distracting if the highlight persisted > (when should it go away?). It should go away on user request. FYI - My Emacs-20 code highlighted grep regexps: - everywhere, in the compilation buffer - one by one, in source-code buffers, when next-error was called. Highlighting the source code this way helps a user keep track of where he's been. The highlighting was persistent. The compilation-buffer highlighting was done with font-lock. I did not provide a way for a user to remove just this regexp highlighting, but that might be useful as a toggle. I know I sometimes toggle search-page highlighting on/off when using the Google toolbar. The source-code regexp highlighting was not done with font-lock. A user could remove it (without affecting font-lock highlighting) in any of several ways: - font-lock-mode twice (easy, if it's bound to a key) - revert the buffer - use my command `highlight' (with negative prefix arg) on a region - ... Drew P.S. Similarly, to help users keep track of lines they've visited, I also highlighted visited line numbers in buffer *Occur*.