Please don't remove the list from discussion. Other people may have
similar issues, and would like to know the resolution.
>>>> "Thoralf" == Thoralf Polet
<polet.thoralf(a)web.de> writes:
Thoralf> Dear Stephen, If you mind the subject of my mail you will
Thoralf> realise the difficulty of that purpose.
Difficult doesn't mean impossible. Crashes in .emacs can often be
avoided with -vanilla, crashes in window system initialization can
often be avoided with -nw. Since your bug report was not very
detailed, I cannot make any assumptions about what you can or can't
do.
At the very least, always send the Installation file which should be
in the platform-specific directory (in this case, probably
i386-redhat-linux). If you can't find that, you should report to the
vendor first, because they will be able to make a better report to us.
Thoralf> xemacs-21.4.14-6.i386.rpm from 2004 Jan 9th seems to work.
Ie, it was a Red Hat problem from the first.
In most cases, Red Hat software is pretty good. However, Emacsen are
a special case because of the way they preload Lisp. Red Hat does a
lot of advanced hacking on the fundamental toolchain and operating
system, and this tends to break Emacsen. "Blame Red Hat first!" :-)
SuSE's just as bad for the X Window System.
You can argue that this is an (X)Emacs design bug, if you like, but
usually there are ways to be backward compatible and (if you want to
continue to use XEmacs) you should insist that your vendors use them.
They provide zero support to us in porting to new environments (NB:
they didn't report your bug to us, although I bet they were aware of
it), so it will be a while before we get around to supporting them.
Although it pains me to say it, there's a good chance that GNU Emacs
will be better supported on these issues.
--
Institute of Policy and Planning Sciences
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.