Re: default-indicate-buffer-boundaries

[Kim F. Storm]

Miles Bader <address@hidden> writes:

> 2006/2/3, Richard M. Stallman <address@hidden>:
>> In the continuation case, we could solve the problem for the
>> end-of-buffer indicator by putting it on the right.  But that won't
>> help in the truncation case.
>
> The code combines indicators for other cases; can't it do so in these?
>
> BTW, before the release I want to change the name of the fringe
> bitmaps so they indicate the _meaning_ of the bitmaps, rather than
> being named after the default appearance... the current names are very
> confusing and inflexible if you change the appearance using
> define-fringe-bitmap.

This is already in FOR RELEASE:

** Rework how fringe bitmaps are defined and used.
Currently, bitmap usage and bitmap appearence are "mixed-up" in a
one-level representation.  It would be cleaner to split the
representation into a two-level model where first level maps
bitmap usage to a bitmap name, and second level maps bitmap name to
a bitmap appearence.
[Assigned to KFS]


I have some of the code written, but I haven't had time to
finish the work.  I'll try to find the time soon.


-- 
Kim F. Storm <address@hidden> http://www.cua.dk