Paul Stodghill <stodghil(a)cs.cornell.edu> writes:
> A. Yes.
At least, in theory it's supposed to. I can't get gnuclient to work
to test it out though....
I am really very impressed with that feat. However why do you need
gnuclient for that?
Just start it up with a native frame and then 'make-frame-on-display'
by hand to make an X frame.
I think that things are even more confused than this. Consider the
following
code in make-faces-bold in faces.el,
(when (featurep 'x)
(frob-face-property face 'font 'x-make-font-bold locale))
(when (featurep 'mswindows)
(frob-face-property face 'font 'mswindows-make-font-bold locale))
When running under CYGWIN+X, doesn't the second "when" expression just
clobber
the results of evaluating the first? This is the behavior that I'm seeing.
I can not argue with experimental results :-)
There are several other places in faces.el where stuff like this is
done...
It doesn't surprise me. the customize isn't really up to handling more
then one device type let alone four (stream, tty, Win32, x). This
needs to mature (and customize needs some rethinking, my hope is that
[given the fact that the current answer on g.e.m to every display
question is "the new display engine in 20.5 will do that"] the FSF
will aslo need to rethink and we can coordinate that. ).
Jan