CS Workstation Editing

If you are connecting to the CS workstations to use graphical applications, you should know that sometimes this is painfully slow. I discourage using eclipse this way, just download it and java at home and transfer the files. Some gui editors, such as gedit and emacs (the graphical version) run with only a little lag, but it can still get annoying. This page is for those who want to edit/compile/run things on our workstations, but don't want to deal with the UI.

Make sure you can work remotely. Here are some resources for getting set up: http://cs.gettysburg.edu/~tneller/dept/remote.html.

My recommendation is find an editor that you like that can work inside a terminal. This includes emacs (my personal favorite), vim and pico (or nano). Pico is by far the easiest as its commands are displayed at the bottom of the screen. It is not feature-rich, but functional.

Run an editor

emacs:

emacs -nw myFile

vim:

vim myFile

pico:

pico myFile

Learn to use the terminal and an editor

• Dr. Neller's Bash tutorial
• List of bash commands
• Emacs Tutorial
• Emacs Quick-Reference
• vim Tutorial
• vim Reference Card

Suggestions

• cd changes your current directory and ls lists the items in it. These will be your most used commands.
• Open up two terminals to a workstation. Leave the editor open in one and use the others to run the compiler or execute the program or whatever it is you are doing with the file.
• Don't forget to save before you switch terminals to compile/run. It is very frustrating when it looks like the compiler didn't catch your last modifications.