🚀 go-pugleaf

In article <1991Jun12.184224.1006@src.honeywell.com>, alarson@SRC.Honeywell.COM (Aaron Larson) writes:
> In article <1991Jun11.165809.3239@bellcore.bellcore.com> dana@dino.bellcore.com (Dana A. Chee) writes:
> 
>    ...I have different color
>    windows for different modes.  What I'd like is to have the foreground
>    set to a color (for an attribute) while the background is set to be
>    the background of the window its used in....

Remember that each screen has a set of local attributes, in addition
to global attributes, so you can override the global attribute with a
screen local one for that screen. I use this for my MH screen code.

> 
> I use the following to approximate this.  What *I* really want is per buffer
> attributes, not per screen.

I've been thinking about this problem for a while. The problem with
buffer local attributes is that the display algorithms are not
sophisticated enough to handle the problems that arise in such a case.
Chris is working on a version to get around this, but it's not
expected anytime soon.

A temporary fix that I've been meaning to implement is to allow a
style color to be set to t, in addition to a color or nil. t would
mean "use the current screen value", so that the problem above could
be solved by setting the background color to t instead of setting up
local styles for every screen that is created. I'll try to do this and
provide a patch in the near future, although it might not be an
official patch.

As a side comment on your code, you might want to be a little careful
with using epoch::create-screen instead of create-screen. The latter
does a number of other things that are desireable, foremost being that
it sets the WM_PROTOCOLS property on the new screen, to indicate that
Epoch will receive WM_PROTOCOL_DELETE messages. Check out the code in
epoch.el for more detail.

-- 
Alan M. Carroll          <-- Another casualty of applied metaphysics
Epoch Development Team   
Urbana Il.               "I hate shopping with the reality-impaired" - Susan