I'm trying to set up the Allegro Common Lisp interface to Emacs. I've
managed this before with ACL 4.3 and Emacs 19.whatever, but now I'm trying
it on a computer with ACL 5.0 and Emacs 20.3.
The symptom: I put the appropriate lines in the .emacs file, it seems to
find everything and start it up, I see everything up to the USER(1):
prompt... and then it just hangs with
Trying to start connection...
in the status line. It really hangs -- I've left it for 10 minutes and no
response. The emacs window it runs in is dead; I have to kill it from the
xterm I started emacs in.
Some more system information:
- operating system: Linux (Redhat 5.2)
- emacs: 20.3 and 20.2 downloaded and compiled from gnu; 20.3 rpm packaged
with Redhat. Same symptoms in all cases.
- lisp: Allegro Common Lisp 5.0 Trial Edition for Linux
Does this sound familiar to anyone? I'm not expert in either lisp or emacs
(doing this for someone else), so I'm kind of at a loss where to go from
here.
Thanks,
MEF
--
Mary Ellen Foster, Department of Computer Science, University of Toronto
Email: ···@cs.utoronto.ca Web: http://www.cs.utoronto.ca/~mef/
--------------------- Law of Software Envelopment: ---------------------
Every program attempts to expand until it can read mail.
Please post any useful e-mail answers you get to this - I have a
completely unrelated application that does exactly the same -
with emacs19 it's fine, but with emacs20 it hangs while trying to
make a connection...
-- Mark
Mark Carroll <·····@chiark.greenend.org.uk> writes:
> [...] with emacs20 it hangs while trying to make a connection...
Does it work to let process-coding-system to `binary' or
`no-conversion' before making the connection?
Hm.
There is network-coding-system-alist; maybe it helps to frob that such
that `binary' or `no-conversion' is used for the connections in
question? (This would not require changes in the existing code.)
But I think I don't grok MULE in fundamental ways. So take this with
a grain of salt.
kai
--
Life is hard and then you die.
I can only show you what worked in my .emacs file:
;; ACL stuff...
(require 'cl)
(push "c:/local/acl50/eli" load-path)
(load "fi-site-init")
;; This function starts up lisp with your defaults.
(defun acl (ide-p)
(interactive "P")
(fi:common-lisp "*common-lisp*" ; fi:common-lisp-buffer-name
;; default-directory ; fi:common-lisp-directory
default-directory
"c:/local/acl50/lisp.exe" ; fi:common-lisp-image-name
fi:common-lisp-image-arguments
fi:common-lisp-host
(if ide-p
"c:/local/acl50/allegro.dxl" ; image-file
"c:/local/acl50/lisp.dxl")
))
;; good luck. dave
···@cs.toronto.edu (Mary Ellen Foster) writes:
> I'm trying to set up the Allegro Common Lisp interface to Emacs. I've
> managed this before with ACL 4.3 and Emacs 19.whatever, but now I'm trying
> it on a computer with ACL 5.0 and Emacs 20.3.
>
> The symptom: I put the appropriate lines in the .emacs file, it seems to
> find everything and start it up, I see everything up to the USER(1):
> prompt... and then it just hangs with
> Trying to start connection...
> in the status line. It really hangs -- I've left it for 10 minutes and no
> response. The emacs window it runs in is dead; I have to kill it from the
> xterm I started emacs in.
hmm some questions:
can you start ACL up in an xterm without emacs?
i put my ACL stuff into /usr/local/acl5
$ /usr/local/acl5/lisp
starts up a lisp for me. i can type simple commands and get a
response. i can also exit fine.
maybe you just need to recompile eli.
i had to hack eli to compile it under emacs 20.*. i forget the file,
but there is some version check. adjust the check to make it accept
newer emacsen or disable it entirely. franz may have fixed this since
i downloaded eli sometime last december.
> Some more system information:
> - operating system: Linux (Redhat 5.2)
> - emacs: 20.3 and 20.2 downloaded and compiled from gnu; 20.3 rpm packaged
> with Redhat. Same symptoms in all cases.
> - lisp: Allegro Common Lisp 5.0 Trial Edition for Linux
this is the same as i use. (well i was using redhat 5.2 plus various
upgrades and hacks until last month and now i am using redhat 6.0.)
> Does this sound familiar to anyone? I'm not expert in either lisp or emacs
> (doing this for someone else), so I'm kind of at a loss where to go from
> here.
i don't recall anything like this happening. however, i do recall
the bit a little with the version check. i am not sure if i didn't
have your problem and that's what drove me to compile eli.
hope this helps.
--
J o h a n K u l l s t a m
[········@ne.mediaone.net]
Don't Fear the Penguin!
···@cs.toronto.edu (Mary Ellen Foster) writes:
> I'm trying to set up the Allegro Common Lisp interface to Emacs. I've
> managed this before with ACL 4.3 and Emacs 19.whatever, but now I'm trying
> it on a computer with ACL 5.0 and Emacs 20.3.
>
> The symptom: I put the appropriate lines in the .emacs file, it seems to
> find everything and start it up, I see everything up to the USER(1):
> prompt... and then it just hangs with
> Trying to start connection...
> in the status line. It really hangs -- I've left it for 10 minutes and no
> response. The emacs window it runs in is dead; I have to kill it from the
> xterm I started emacs in.
>
> Some more system information:
> - operating system: Linux (Redhat 5.2)
> - emacs: 20.3 and 20.2 downloaded and compiled from gnu; 20.3 rpm packaged
> with Redhat. Same symptoms in all cases.
> - lisp: Allegro Common Lisp 5.0 Trial Edition for Linux
>
> Does this sound familiar to anyone? I'm not expert in either lisp or emacs
> (doing this for someone else), so I'm kind of at a loss where to go from
> here.
>
> Thanks,
>
> MEF
>
> --
> Mary Ellen Foster, Department of Computer Science, University of Toronto
> Email: ···@cs.utoronto.ca Web: http://www.cs.utoronto.ca/~mef/
> --------------------- Law of Software Envelopment: ---------------------
> Every program attempts to expand until it can read mail.
Mary,
Do you have a network connection? I saw just this behaviour when I
tried to run ACL 5.0 on my Linux box (with no permanent network
connection). When fi:common-lisp asks for a Host, try entering
'localhost' (without the quotes). That did it for me. I now have
(setq fi:common-lisp-host "localhost")
in my .emacs, in addition to the other ACL stuff. This makes localhost
the default, saving a bit of typing.
HTH,
Barry Wilkes.
The problem I posted about was that when I tried to start up the Allegro
Common Lisp 5.0 interface in emacs 20.3, it would hang during the process
of starting the connection, and I wondered whether it was something in
emacs or ACL causing the problem.
Well, during the course of configuring other things on the computer, I
realized that its hostname was configured oddly -- no /etc/hosts file (it
is a standalone Linux box that never connects to a network). After putting
the standard
127.0.0.1 localhost localhost.localdomain <hostname>
line in there, I started getting different errors along the lines of
"permission denied", and a diagnostic message to the effect that if "rsh
<hostname> date" didn't work, then the emacs interface wouldn't work
either.
So, I made "rsh <hostname> date" work (currently with some .rhosts files,
but I'll see if I can find a better way), and lo and behold, the emacs-acl
interface started up with no further problems!
Thanks for all the responses, most of which basically said "this works for
me, so it should work for you too" and made me look at other possible
causes. :-)
MEF
--
Mary Ellen Foster, Department of Computer Science, University of Toronto
Email: ···@cs.utoronto.ca Web: http://www.cs.utoronto.ca/~mef/
--------------------- Law of Software Envelopment: ---------------------
Every program attempts to expand until it can read mail.