From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: ytrewq1 Newsgroups: gmane.emacs.help Subject: Re: header-line-format hacking Date: Mon, 31 Jan 2005 23:43:49 +0000 (UTC) Message-ID: References: <87pszl3772.fsf-monnier+gnu.emacs.help@gnu.org> 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 1107215315 20252 80.91.229.6 (31 Jan 2005 23:48:35 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 31 Jan 2005 23:48:35 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Feb 01 00:48:22 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CvlHJ-0002M4-00 for ; Tue, 01 Feb 2005 00:48:21 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CvlRn-0000w6-EI for geh-help-gnu-emacs@m.gmane.org; Mon, 31 Jan 2005 18:59:11 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1CvlRP-0000lB-9i for help-gnu-emacs@gnu.org; Mon, 31 Jan 2005 18:58:47 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1CvlRH-0000hS-2R for help-gnu-emacs@gnu.org; Mon, 31 Jan 2005 18:58:40 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CvlRG-0000gx-RR for help-gnu-emacs@gnu.org; Mon, 31 Jan 2005 18:58:38 -0500 Original-Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1CvlDH-0000OE-6w for help-gnu-emacs@gnu.org; Mon, 31 Jan 2005 18:44:11 -0500 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1CvlCy-0007sO-PM for help-gnu-emacs@gnu.org; Tue, 01 Feb 2005 00:43:52 +0100 Original-Received: from p2113-ipbf613marunouchi.tokyo.ocn.ne.jp ([222.149.225.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 01 Feb 2005 00:43:52 +0100 Original-Received: from ytrewq1 by p2113-ipbf613marunouchi.tokyo.ocn.ne.jp with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 01 Feb 2005 00:43:52 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-To: help-gnu-emacs@gnu.org Original-Lines: 39 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: main.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 222.149.225.113 (Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0) X-Gmane-MailScanner: Found to be clean X-Gmane-MailScanner: Found to be clean X-MailScanner-From: geh-help-gnu-emacs@m.gmane.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.help:23793 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:23793 Stefan Monnier writes: > There are currently few uses of the header-line, and most of them seem to be > "global". I.e. either it's absent, or its content does not naturally lend > itself to being accompanied with some other info. > > Could you give a couple examples of the kind of things you'd like to put/add > into the header-line? I'm writing a couple of minor modes in which I'd like to express certain 'state' information and I'm not finding a whole lot of space in the mode line on my system. One minor mode attempts to display the current 'class' that point is in -- similar to what which-function-mode does for functions [1]. On my system, there doesn't seem to be enough space to display this in the mode line -- especially when which-function-mode is active. The other mode is for creating navigable annotated 'traces' through source code. Roughly, a reader of some source code is provided with a way of keeping notes as the flow of execution is traced. At the moment this happens by selecting regions of text, indicating that a selected region is a call or a definition, and optionally associating some text. The created 'traces' may be navigated (e.g. move to root of trace, move to next annotated point of execution, etc.), edited, and shared. Anyway, I'd like to express the idea of 'trace has been modified' in a way similar to what's currently done for 'buffer has been modified'. I'm also thinking of expressing some other trace-related state information but I wanted to see if I was able to work with header-line-format appropriately before exploring the idea further. Needless to say, I'd like to use both of these modes at the same time -- which is what prompted my question. [1] In fact, which-class.el is essentially a modified which-func.el.