From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: fringe buffer-boundary bitmaps Date: Fri, 24 Jun 2005 10:37:12 +0200 Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1119603687 20536 80.91.229.2 (24 Jun 2005 09:01:27 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 24 Jun 2005 09:01:27 +0000 (UTC) Cc: emacs-devel@gnu.org, miles@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jun 24 11:01:21 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Dlk3E-0004cl-Gd for ged-emacs-devel@m.gmane.org; Fri, 24 Jun 2005 11:00:40 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DlkAE-0004qe-Fh for ged-emacs-devel@m.gmane.org; Fri, 24 Jun 2005 05:07:54 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Dlk90-0004SG-Vr for emacs-devel@gnu.org; Fri, 24 Jun 2005 05:06:39 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Dlk7D-0003kK-CD for emacs-devel@gnu.org; Fri, 24 Jun 2005 05:04:53 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Dlk77-0003KY-Rl for emacs-devel@gnu.org; Fri, 24 Jun 2005 05:04:42 -0400 Original-Received: from [195.41.46.237] (helo=pfepc.post.tele.dk) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DljkO-0000nH-VU; Fri, 24 Jun 2005 04:41:13 -0400 Original-Received: from kfs-l.imdomain.dk.cua.dk (unknown [80.165.4.124]) by pfepc.post.tele.dk (Postfix) with SMTP id F0CB12628B8; Fri, 24 Jun 2005 10:37:32 +0200 (CEST) Original-To: rms@gnu.org In-Reply-To: (Richard M. Stallman's message of "Fri, 24 Jun 2005 01:36:00 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) 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:39417 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:39417 "Richard M. Stallman" writes: > > indicate-buffer-boundaries would be the place to specify this. > > I don't see why the mapping should be restricted to just the bitmaps > used for buffer boundaries ? > > As far as I know, these bitmaps are used in two ways. You can specify > them by name, in a display property, and certain fixed bitmap names > are used for specific standard purposes. > > In the case of the display property, you can give the bitmap any name > you like; the display property specifies which name to use. > > My proposal is to create a similar level of specifying the name for > the specific standard purposes. I understand that, but I don't see why we need two different ways to modify them -- you can redefine the standard bitmap directly, so I don't see why do we need an extra level of indirection here (which has to be done at the C level to an already quite complex piece of code). Currently, what we have are standard bitmaps for "bob-left", "bob-right", "eob-left", "eob-right" etc... But, rather than following the existing pattern of naming them after their purpose (like "continuation-line", "left-truncation" etc), I have named them after their visual appearence, e.g. "top-left-angle", "top-right-angle", "bottom-left-angle", etc... That is a bug IMO, so I agree with Miles that those names should be changed to match their purpose rather their appearence. If we do that, the extra level of indirection you suggested is not necessary. The relevant bitmaps that should be renamed are: up-arrow => top-scroll down-arrow => bottom-scroll top-left-angle => left-beginning-of-buffer top-right-angle => right-beginning-of-buffer bottom-left-angle => left-end-of-buffer bottom-right-angle => right-end-of-buffer left-bracket => left-all-of-buffer right-bracket => right-all-of-buffer -- Kim F. Storm http://www.cua.dk