Date: Tue, 14 Jan 1997 20:06:54 GMT Server: Apache/1.0.3 Content-type: text/html Content-length: 5346 Last-modified: Thu, 05 Sep 1996 17:47:55 GMT
This general information page was written by Kelly Hall who was the last TA fro this class and is updated for use this semester.
If you hate Unix machines, Gofer is available for almost any kind of computer around. Send me mail for details. You can easily run this on PCs, Macs, Amigas, STs, whatever. It will probably even run on the Y-Vax. The rest of this page will cover running Gofer on the LAL machines; if you run Gofer elsewhere, check this out first.
There are no facist disk quotas on the LAL machines. All I ask is that you keep your usage to reasonable levels. Follow this vague request and they'll be plenty of resources for everyone.
If you forget to set the terminal type when you log in, you can do it
later by isssuing the command: export TERM=xterm
at the
Unix prompt. Of course, if you don't want xterm you can specify
whatever you want.
Now that the terminal type is set, make sure you set your default editor. We have emacs, vi, and the Vuepad editors available on the LAL machines. Pick whichever one you want to use with Gofer and issue the appropriate command below:
export EDITOR=/usr/local/bin/emacs
export EDITOR=/usr/bin/vi
export EDITOR=/usr/vue/bin/vuepad
(Clever users will stick these commands into the file .profile and forget about this. Note: this is .profile and not .login for any of you archaic C-shell users.)
The commands you'll probably use most often are :edit and :load Start up an editor from within Gofer by typing :edit <filename> where you can replace <filename> with the name of a text file (try foo.g). This should start up the editor you specified earlier. Add a couple of the example expressions from the Gofer/Haskell tutorial and save the file.
Exit your editor and Gofer should resume. Load the file you just edited by issuing the command :load <filename> Hopefully there were no errors and Gofer will print out the results of evaluating the stuff in your file. In any case, you can go back and edit that file again by issuing another :edit <filename> command. This process repeats until you get tired of Gofer an exit with the :quit command.
You could just type those expressions straight into Gofer to evaluate, but then you'd have to type them over and over again whenever you started up Gofer. Using a editor and a text file lets you save your work.