Hi,
Esben Mose Hansen <kde@xxxxxxxxxxxxx> writes:
> On Tuesday 2005-02-15 20:59, you wrote:
>> Hi,
>
> argh! Top quoted. Amputating quote in an attempt to save the post
> ;-)
Yes, well, I was in a hurry.
>> 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!
Great, then mabye we'll manage to use that patch. SXEmacs is a recent
XEmacs fork, for you info.
>> 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. But normally, programming directly again X(t)
> isn't worth the bother ... there are many nice toolkits out there
> (Qt, GTK+, vxwindows and others).
I know about the others, but I think I'll still want to fix the
current X code in SXEmacs occasionally. I will be doing Qt stuff soon
too.
> 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 :)
No, but I'm getting there ;)
Johann
--
This line is left blank intentionally
|