Re: Xft
Mats Lidell writes:
Why not make --with-xft=emacs,nomenubars,notabs,nogauges as you
suggest the quick fix? This will make users specifying --with-xft=yes
happier.
Because AFAICS it's not quick. The only way we currently have to do
that is to initialize _with_xft_emacs=yes, which will mean that
somebody who omits --with-xft entirely will be shocked when they start
XEmacs the next time. Hopefully pleasantly, but in the current state
of Xft a large minority will find it yucky to unusable.
For the future a situations where XE_COMPLEX_OPTION has only
"no" as
default, making "--with-XYZ=yes" a noop, I suggest making that a
configuration error, eg configure should complain.
Well, no, that's not really right since we can do better.
"./configure ..." (no --with-xft option at all) currently doesn't do
any Xft since I'm sufficiently unhappy with its current state
(specifically docs and the cursor turds that some fonts leave behind)
that I don't want to recommend it. This is not a bug.
"./configure --with-xft=yes" should be enough for the user to get the
"most useful, safe for a beta tester" configuration (which IMO is
"--with-xft=none,emacs"). The fact that currently it does nothing is
a bug.
Now, suppose I get fired or something nice like that so I have time to
fix the tabs to handle non-Latin-1 fonts, and I do. In that case, I
would like "--with-xft=yes" to automagically "upgrade" to
"--with-xft=none,emacs,tabs". Don't you think that is the right thing?
Just mentioning it in Installation is not clear enough.
Agreed.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta