New subject: Customize bug?

Tuesday, 16 March 1999

        Per Abrahamsen <abraham(a)dina.kvl.dk&gt; writes:

...
 Jan Vroonhof <vroonhof(a)math.ethz.ch&gt; writes:

 > Because the custom font-model is based on the FSF font model and
 > ignores the specifier system completely. 

 It isn't based on the "FSF font model", as there is no such thing.  It is
 based on the pre-specifier *face* model, plus a subset of wmperrys
 font.el package, the closest thing you get to a *font* model on either
 emacs. 
font.el now has pretty full support for the new Emacs redisplay code as
well, so if custom continues to use some subset of font.el, it should work
'out of the box'.

...
 > In FSF Emacs this is trivial since customize exactly matches the
FSF
 > font model. Adapting customize to more powerful font models (whether
 > for XEmacs or for FSF 20.5+) without overly complicating the
 > interface will be a challenge.

 There is no XEmacs font model, which is the only hard thing about it.  I
 discussed with wmperry how to make it use the full font.el font model,
 that's not hard, it is just a small matter of programming. 
I would dearly love to see this change.  Perhaps the new Emacs redisplay
will force us to do it. :)  The merging of font properties is very nice and 
powerful.

-Bill P.

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Re: Customize bug?