[plt-scheme] Fwd: osx jaguar

I've been able to use Quack under Emacs 21.3.50.1 on Jaguar (10.2.1).  
Make sure your .emacs says at least the following:

;;;
;; substitute the location of your quack.el for the last arg.
(add-to-list 'load-path "~/Library/emacs/quack")

;; substitute the location of your mzscheme executable for the last arg.
(add-to-list 'exec-path "~/plt/bin")

(require 'quack)
;;;

Then "M-x run-scheme" should do the right thing.

hth
Dale

On Tuesday, October 29, 2002, at 06:35  PM, Dennis Groves wrote:

>  For list-related administrative tasks:
>  http://list.cs.brown.edu/mailman/listinfo/plt-scheme
>
> Interesting that did indeed work for me.
> What I was attempting to do was this get it to work with quack.el 
> found here http://www.neilvandyke.org/quack/
> Another attempt was to get it to work with iLisp found at 
> http://sourceforge.net/project/showfiles.php?group_id=3957
>
> I had hoped to have an emacs environment that was similar to Dr.Scheme.
>
> Dennis
>
>
> On Tuesday, October 29, 2002, at 02:59  pm, John Clements wrote:
>
>>  For list-related administrative tasks:
>>  http://list.cs.brown.edu/mailman/listinfo/plt-scheme
>>
>>
>> On Tuesday, October 29, 2002, at 04:13  PM, Dennis Groves wrote:
>>
>>>  For list-related administrative tasks:
>>>  http://list.cs.brown.edu/mailman/listinfo/plt-scheme
>>>
>>> If I try and run mzscheme as an inferior emacs process under jaguar 
>>> the process terminates.
>>> Does anybody have any insights into what the problem is and how to 
>>> correct it?
>>>
>>
>> Can you supply more details?
>>
>> I started Emacs, opened a shell with M-x shell, and then invoked 
>> mzscheme:
>>
>> tcsh: No entry for terminal type "emacs"
>> tcsh: using dumb terminal settings.
>> [osterley:/] clements% ~/plt/bin/mzscheme
>> Welcome to MzScheme version 202.5, Copyright (c) 1995-2002 PLT
>> > (+ 3 4)
>> 7
>> > (exit)
>> [osterley:/] clements%
>>
>>
>> As you can see, it worked fine[*].  Are you referring to some set of 
>> .el bindings for scheme?
>>
>> john
>>
>> *: ... except for the $PATH not getting set.  Is this perhaps your 
>> problem?
>>
>>
>
>
--
Dale Vaillancourt
dalev at ccs.neu.edu