🚀 go-pugleaf

Emmett McLean writes:
 > Does anyone have  supplemental documentation on how to
 > use the interactive smalltalk commands such as
 > smalltalk-doit, smalltalk-compile, and smalltalk-snapshot?
 > 
 > My path set up so st.el finds mst and
 > when I type "M-x mst" I get the desired two window 
 > set up. If anyone is really ambitous they might
 > I instruct mst to evaluate the last 10 lines of code
 > below.
 > 
 > Your help is greatly appreciated. By helping me you are
 > also helping about 10 other students who find this of interest.

Hi -- sorry to take so long to reply.  Let's see...you want to understand how
to work the Emacs "browser".  There is some description of this facility in the
mst.textinfo file that you should have in the 1.1.1 distribution.  Basically,
if you are evaluating some code for immediate execution, put the cursor
somewhere in the code and type C-c d (control-c d).  This will send the
expression to Smalltalk (invoking a session if there isn't one).  In the case
of the last 10 lines of the code, you've defeated the heuristic for the
smalltalk-doit Emacs function: you need to indent the code (even by one space)
for c-c d to work.  

|m l o count|
    l_ GraphNode new.
    m_ GraphNode new.
    o_ GraphNode new.
    l addNeighbor: m.
    l addNeighbor: o.
    count_0.
    (l doWithNeighbors: [count_count+1]).
    count printNl
!

I'd also recomment strongly putting in spaces around the assignment and the 
+ operators.  

Now, even for the code you have, you can force evaluation of particular areas
of code with the c-c e command (smalltalk-eval-region).  Put a mark at one end
of the expression (region) to be evaluated, and move the point (cursor) to the
other, then type c-c e.  

To compile individual methods, put the cursor somewhere inside the body and
type c-c c.  To compile whole sections of your program, use c-c e around the
entire set of method definitions (including the "methodsFor:" part).

Steve