Henry Lenzi <[EMAIL PROTECTED]> writes: > Chris Baker <electro <at> 1939worldsfair.com> writes:
[...] >> I have this problem intermittantly, but I've never been able to track >> down a reproducible case. It only happens when you get an error after >> clm is loaded but using the inspector. >> > > Interesting. I guess the inspector did load (pretty emotional sighting, > actually, for me). > >> To get this to work: >> >> 1. Make sure you aren't running any stray copies of motifd (the >> server process). >> > Do I simply do ./motidf ? How do I start this server? Generally cmucl will run motifd for you. When I was screwing around with it, I would sometimes end up with multiple copies of it running, which cmucl would try to reuse even if it was in a messed up state. That's why I recommend checking to see if there are any other copies running before proceding. >> 2. Clean out any stray .motif* files in your /tmp directories. >> > Will these files be generated automagically in /tmp? Yes, motifd creates one when it starts. That's how clm knows whether it needs to start one or not and what port to connect to. > And what about the other variables, for instance, xtk::*default-binary* and > such in the CLM manual? Do you set them at all? Heh. I've not seen the manual you're refering to, but I suspect it might not be the right one. There are, unhappily, two different motif interfaces (plus Common Lisp Music, which also goes by CLM). The cliki entry for CLM explains this better than I could: http://www.cliki.net/CLM Your manual is probably for the wrong one. Try this one: http://www.pmsf.de/pub/cmucl/doc/motif-toolkit.pdf Best wishes, cbb -- 20:38:42 up 12:46, 0 users, load average: 0.01, 0.05, 0.02
