>>>>> "MP" == Malcolm Purvis <malcolmp(a)xemacs.org> writes:
>>>>> "Joachim" == Joachim Schrod <jschrod(a)acm.org> writes:
Joachim> Anyhow, I don't care much; I just wanted to help.
MP> My apologies for the response your patch has received.
I don't take it as a problem, no apologies needed. My reaction might
have been misunderstood -- I'm not pissed off, I just should have
asked before I spent the work preparing the patch.
In fact, I can understand Steve who's worrying that the right solution
will not arrive any time now -- but I don't agree with him that the
`right' solution will arrive earlier by not fixing the current system.
In particular, since the current system is announced on the Web Site
as `the way to do it' and that way doesn't work without errors any
more. As far as I follow xemacs-beta, reworking build seems to be very
low on the priority list, and it's not as if the XEmacs development
team would have free time right now. ;-)
This is no big deal anyhow. I just switched to SUSE 10.0, and when the
distribution's XEmacs wasn't able to do package updates, I compiled a
new one by myself. Then I discovered Build and used it. (I even sent a
build report that somehow didn't make it to the list.) When I got
errors from the configure call created by build, I recognized that
they are due to an out-of-date configure.usage and made the patch.
Besides, I'm being used that patches from me are mentioned for almost
a decade in the FAQ (about a changed cl-indent.el that I posted to
c.e.x in 1994), get not integrated, and then get discarded in December
by Ben. :-) :-)
Joachim> Next time I'll spend the evening with my wife, instead of
Joachim> preparing an unannounced patch. ;-)
Please note: the emphasis was on `unannounced'. In retrospect, I see
that meaning is not visible enough.
MP> Why not do both? As I type this my wife is sitting beside me, in
MP> front of her computer, breastfeeding our 5 month old and flaming
MP> some loser on misc.kids.
I also have the luck that my wife is a geek. (If you happen to own a
2nd ed. of the LaTeX Companion, a picture of us is on the last
biography page. :-) But we also spend quite some time to run an IT
company, and learned the hard way in the last 24 years that one needs
to be careful to take one's time off, too. So I try to spend work in
Open Source projects only when I'm reasonably sure that it sits well
with the current development team.
Joachim Schrod Email: jschrod(a)acm.org
``How do we persuade new users that spreading fonts across the
page like peanut butter across hot toast is not necessarily the
route to typographic excellence?'' -- Peter Flynn