In the future, please follow up to the mailing list. That way others
will know that this problem can be solved/worked around this way.
(This time my post is sufficient.)
François Jouve writes:
Kevin Oberman wrote:
> One other thing to check/try...do you have an entry for your
system in
> your hosts file? If not, it may be trying a DNS lookup and failing.
It works ! Thank's *a lot* for your help. I have been searching
for monthes this answer. Actually my /etc/hosts was :
127.0.0.1 localhost.localdomain localhost myhostname
and I changed it into
127.0.0.1 localhost.localdomain localhost myhostname myhostname.my.domain
PS: I know that you are not responsible for that but the version
21.5.27
of xemacs (which is a beta version) is very buggy. You get the message :
"Invalid constant: Unrecognized coding category iso-8859-1"
Unfortunately, it is the version that is present in the new fedora core 6
distribution...
It's also apparently not a bug in our distribution---I've never heard
of it before. If you have access to it, try whatever gives that
message under "xemacs -q" (to make sure it's not something in your
init file), and if it still happens, send them a report.
We'd be happy to help, but this looks like a typo to me (the coding
category is iso-8-1)---just grepping the rpm patchset should uncover
it quickly.
There is no problem to downgrade it to the latest stable version
(21.4.19),
but a bug-free version in a brand new distrib may be a better idea :)
*chortle* I have yet to hear a good word about FC6. All the Fedora
users I know are bitching about new driver and app bugs.
I'm sure it's got lots and lots of good stuff (sez me as I type into a
Mac OS X 10.3.9 Terminal displaying XEmacs running on a Gentoo Linux
system:-), but Fedora is about "many eyes, shallow bugs", not about
stability.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta