| ||
Getting Started: GNU Emacs Integration |
To obtain an environment which has much better scalability for programs consisting of many fragment groups (source code files), try to run gbeta from GNU Emacs. This environment offers a more "visually" oriented interaction as well. Setting up Emacs
Assuming that you have access to GNU Emacs and already use it, you
probably have a file
gbeta.emacs in the distribution.
Starting Emacs, under X..
Initially, go to the
Some Emacs terminologyEmacs may have more than one "frame," and each frame may have more than one "window." Since the Emacs terminology collides with the general terminology of common GUIs, we'll shortly recapitulate the Emacs terms here: An Emacs frame is the graphical unit which is decorated by the window manager (e.g. with a titlebar and a border), and which can be moved, resized, iconified, raised, lowered, and so on. An Emacs window is a vertical or horizontal band of an Emacs frame, showing a portion of one buffer. These concepts are important because there is normally an interpreter window showing an interpretation (Emacs thinks: debugging) buffer, and a source code window showing one of a number of source code buffers containing the program being interpreted. The interaction is different when the interpretation window is active and when the source code window is active. Starting the interpretationTo initiate an interactive execution of the program in the newly loaded buffer, ensure that the window showing that buffer is the currently active window (click in it). Then do:
"gbeta[ENTER]" . This leads
to a prompt in the bottommost line of the frame (the "minibuffer"):
[ENTER] is appropriate.
This starts up an interactive gbeta session in one window and shows the source code file containing the first statement of the program in another window. The file shown is not necessarily the same as the argument given to gbeta, since the fragment system makes it possible to insert your program into some larger context. The next section deals with the interaction within an Emacs-based gbeta session. As a rule of thumb, however, you can just start using what you already know from the command line interaction. |