Ar an cúigiú lá déag de mí Feabhra, scríobh Esben Mose Hansen:
> I've reproduced the following with my copy of sexy, this is
therefore
> a bugreport for us. At least I think so. It really doesn't surprise
> me if XE developers ignore this though.
Actually, I got an indication from Mr. Aidan Kehoe that he would fix
this. And many thanks for that!
I’m not keeping to my stated schedule, though, am I ;-) . I have spent a
good bit of this evening working on selection fixes, though. It seems subtly
broken in so many ways--for example, if XEmacs is linked against Motif,
it’ll only ever offer TARGETS, TIMESTAMP, STRING or COMPOUND_TEXT to pass
out, despite paragraphs and paragraphs of Lisp occupied with doing that
better.
> If I can find out anything about X programming, I may attempt to
fix
> this. If anyone else can, please be my guest. I'd also like some
> pointers about how to learn X (Xt?) programming.
man XLib is a start.
Also,
http://ftp.xfree86.org/pub/XFree86/4.4.0/doc/PDF/xlib.pdf .
But normally, programming directly again X(t) isn't worth the
bother
... there are many nice toolkits out there (Qt, GTK+, vxwindows and
others).
But, unfortunately, their implementations are not that finished on XEmacs,
so there’s a need to learn the X library to finish them.
But unless you are used to hacking XEmacs, XEmacs itself might be a
bigger
stumbling block. Even getting that beast to build is a challenge :)
Hmm, I’ve found it one of the more sane OSS projects I’ve built.
--
“Ah come on now Ted, a Volkswagen with a mind of its own, driving all over
the place and going mad, if that’s not scary I don’t know what is.”