From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: [jidanni@deadspam.com: modeline doesn't divulge buffer will go bye bye] Date: 21 Jun 2002 01:27:52 +0200 Sender: emacs-devel-admin@gnu.org Message-ID: <5xu1nxh6o7.fsf@kfs2.cua.dk> References: <200206201435.g5KEZLF18772@aztec.santafe.edu> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1024612214 24399 127.0.0.1 (20 Jun 2002 22:30:14 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Thu, 20 Jun 2002 22:30:14 +0000 (UTC) Cc: emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17LARS-0006LQ-00 for ; Fri, 21 Jun 2002 00:30:14 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 17LAtK-000243-00 for ; Fri, 21 Jun 2002 00:59:02 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17LARR-0002Z5-00; Thu, 20 Jun 2002 18:30:13 -0400 Original-Received: from mail.filanet.dk ([195.215.206.179]) by fencepost.gnu.org with smtp (Exim 3.34 #1 (Debian)) id 17LAOW-0002Jf-00 for ; Thu, 20 Jun 2002 18:27:12 -0400 Original-Received: from kfs2.cua.dk.cua.dk (unknown [10.1.82.3]) by mail.filanet.dk (Postfix) with SMTP id 6F1607C016; Thu, 20 Jun 2002 22:27:11 +0000 (GMT) Original-To: bob@rattlesnake.com In-Reply-To: Original-Lines: 43 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.9 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:5029 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:5029 "Robert J. Chassell" writes: > What do you think of this idea? > > The most important thing, the fact that this buffer will go > bye bye without a trace is not mentioned there! > Hm, most non-file buffer names created automatically by various packages start (and end) with an asterisk. So for such buffers, there typically already is a visible difference in the mode-line. The problem is with buffers which the user creates explicitly. Such buffers are typically named like a file (except that they typically don't have a file name suffix). Personally, I choose dummy names for my own non-file buffers, so I rarely confuse a non-file buffer with a file buffer. Of course, if I name my temporary buffers file.c -- I'm asking for trouble :-) I really think this is a non-issue (it actually took Dan 20 years to be aware that there was a problem :-) > Perhaps we could insert a dot in a space to the left of the > `mode-line-frame-identification' segment of a mode line if the buffer > is visiting a file, and replace that glyph with a blank space if the > buffer is not associated with a file. > > I pick `dot' as the visible glyph since it is small, unobtrusive, and > should not make the mode-line appear too cramped. I don't think this will do the trick. For one thing, I think that if we choose to make some annotation, it should be on the non-file buffers (which are the dangerous ones to kill). Maybe we could write [TMP] before the buffer name for non-file buffers. But not do this for buffer names starting with an *. -- Kim F. Storm http://www.cua.dk