Stephen J. Turnbull writes:
Jeff> it's not documented. --with-widgets isn't even
mentioned in
Jeff> the INSTALL file.
That's a bug in the INSTALL file, then.
true... just pointing it out.
Jeff> if you do "configure --help" it tell you that
"lucid, motif,
Jeff> athena, or no" are the metioned options.
A bug in configure.usage. I believe gtk and yes are also accepted.
It's possible that a patch got overlooked here, as ISTR somebody
submitting a patch to synch configure.usage to reality.
i think you are right... if you grep configure, it lists gtk & yes in
one of of the widget error msgs...
Jeff> And when people look in PROBLEMS, will that help them?
no.
I don't see a PROBLEM, here, once the documentation is fixed.
ok... but it's a problem until then. :)
Jeff> buffers are pretty useless without them.
They had better not be useless! Ugly, OK, but not useless. If they
are, that's a bug in the implementation of the widgets or the
particular platform. Custom has some ugly bitmaps that it uses when
native buttons and toggles aren't available.
well, something broke then. I get the same cutomize buffer that Vaclav
sent a screenshot of if I just run "./configure"
ugly would be better than missing. :) and I guess ugly is in the eye
of the beholder. the xpm glyphs were better looking to me than the
crappy Xaw buttons I see.
I will try it with --with-gtk=yes and see how things look
As I say, a rework of configure to get the toolkits right would be a
good idea. But there were a couple of people who were not getting an
xemacs if they simply used ./configure.
i thought that had been done. Didn't someone do a major reworking
for all the various Xaw variants awhile ago? If I remember right,
wasn't that the main cause of the configure foulups? people
installing Xaw3d and such as Xaw.