[OT?] chasen.el problem
I made several experiments with Emacs interfaces to dict and other
servers; my last try was chasen from Debian distribution. Emacs seems
to hang after the call to `open-network-stream', while command line
clients work correctly.
I tried to use strace to learn more.
When I call
chasen -Dlocalhost:31000 chasen.in
it connects to the server with
connect(4, {sin_family=AF_INET, sin_port=htons(31000), sin_addr=inet_addr("127.0.0.1")}}, 16) = 0
and everything in OK.
When I try to use chasen.el interface included in the Debian package,
the call to `chasen-region' boils down to the call to
`open-network-stream', and strace shows that Emacs is in the following
loop:
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 4
sendto(4, "\37\6\1\0\0\1\0\0\0\0\0\0\tlocalhost\5mimuw\3edu"..., 40, 0, {sin_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("148.81.13.1")}}, 16) = 40
time(NULL) = 996807666
poll([{fd=4, events=POLLIN}], 1, 5000) = 0
close(4) = 0
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 4
sendto(4, "\37\6\1\0\0\1\0\0\0\0\0\0\tlocalhost\5mimuw\3edu"..., 40, 0, {sin_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("148.81.12.1")}}, 16) = 40
time(NULL) = 996807671
poll([{fd=4, events=POLLIN}], 1, 3000) = 0
close(4) = 0
etc.
These tests are made on a notebook configured for a specific network,
but actually not connected. There is an evident difference in
interpreting "localhost" by Emacs and command line client, but I don't
know if this is relevant.
How to debug the problems? Is anybody using chasen.el succesfully?
Regards
Janusz
--
,
dr hab. Janusz S. Bien, prof. UW
Prof. Janusz S. Bien, Warsaw Uniwersity
http://www.orient.uw.edu.pl/~jsbien/
---------------------------------------------------------------------
Na tym koncie czytam i wysylam poczte i wiadomosci offline.
On this account I read/post mail/news offline.
Reply to: