Procedures - LSU EE 4720

Account Setup (Updated Spring 2022)

To Setup Account for use with SPIM, PSE and Other Software

The instructions below setup your account so that it can use the SPIM MIPS simulator, the PSE simulation viewer and the Emacs initialization file. The setup can be run from any ECE Linux machine. Because of frequent changes to ECE Linux systems it's possible that the setup routine won't work. Please report any problems promptly for friendly, non-judgmental help so that you can quickly get started on your assignment.

Locate a Linux workstation in the back of the ECE workstation laboratory, Room 2241 Patrick F. Taylor Hall. The host names of suitable machines can be found on the Computer Status page under the Host Name column. Find a machine with a matching label on the front. The labels might only show the first component of the domain name, for example, pulsar instead of pulsar.ece.lsu.edu. It might be necessary to wake up the machines by moving the mouse or pressing the Shift key. Their screens will initially show the time with a slide-up chevron-shaped symbol. Slide the chevron up using the mouse. A login screen should slide in to view displaying some kind of Red Hat Enterprise Linux text or logo.
Log into a Linux machine with your class account.
The accounts were (or will be) distributed by E-mail. All passwords start with the characters 2@W, followed by a random string of eight lower-case letters. When you first log in a Gnome graphical desktop should appear.
Start a shell (command-line interpretor). One way to do this is to right-click the desktop and select Open Terminal.
A window with Terminal in the title should appear with a Unix prompt. If this looks scary you might need to brush up on Unix commands.
Run the setup routine by typing:
[xyz.ece.lsu.edu]% /home/faculty/koppel/pub/ee4720/bin/setup Finished copying 4 files. Log out then log in again.

Yes, that's alot to type. However you can save time by pressing the Tab key at certain times, specifically when enough of a path component has been typed to disambiguate the rest. For example, try pressing Tab after just typing /home/f. It should finish the input with faculty. The setup routine will modify your .bashrc and .emacs files. The .bashrc file sets up your account each time you log in (more precisely, each time you create a shell). The .emacs file contains preferences for the Emacs text editor. The only change made to these files is to include other files, so it's okay to edit them. It's also safe to run setup multiple times, though that should not ordinarily be necessary.
Log out and then log back in.

MIPS Homework and Practice Work Flow (Spring 2022)

Basic Steps

This procedure shows the basic steps needed to work on a MIPS programming homework assignment and practice problems. These steps are written for a 2021 Homework 1, but can easily be adapted to other assignments by changing references to the year and to the homework number, say from /home/faculty/koppel/pub/ee4720/hw/2021/hw01 to /home/faculty/koppel/pub/ee4720/hw/2038/hw32.

Follow the instructions above for setting up the class account.
Copy the practice files into your class account. Here is how to do so from a command shell:
[xyz.ece.lsu.edu]% cd ~ Change to your home directory. /home/classes/ee4720/ee472000 [xyz.ece.lsu.edu]% cp -r /home/faculty/koppel/pub/ee4720/hw/practice .

Don't miss the dot at the end of the command. This copies the practice directory into your class account. You should know how to browse the files in the directory, edit, copy, delete them, etc. If the practice files have been updated you can copy the directory again. You might want to rename your copy so that the work you've done does not get overwritten. To rename (move in Unix parlance) a directory mv practice old-practice. This may be a good time to practice your Unix shell (command-line interface) skills.
Verify that files were copied and look at what's there.
[xyz.ece.lsu.edu]% cd ~/practice Change to directory HOME/practice. /home/classes/ee4720/ee472000/practice [xyz.ece.lsu.edu]% ls -la List directory, long format, show all files. total 44 drwxr-xr-x 2 ee472000 ad4720 4096 Jan 17 12:53 . drwxr-x--- 8 ee472000 ad4720 4096 Jan 17 12:53 .. -rw-r--r-- 1 ee472000 ad4720 3157 Jan 17 12:53 hex-string-live.s -rw-r--r-- 1 ee472000 ad4720 4418 Jan 17 12:53 hex-string.s -rw-r--r-- 1 ee472000 ad4720 4918 Jan 17 12:53 histo-live.s -rw-r--r-- 1 ee472000 ad4720 5453 Jan 17 12:53 histo.s -rw-r--r-- 1 ee472000 ad4720 1077 Jan 17 12:53 strlen-live.s -rw-r--r-- 1 ee472000 ad4720 1394 Jan 17 12:53 strlen.s

Your directory listing may contain a different collection of files. There are two versions of each practice program. The ones with -live in the name are not solved.
Copy the assignment files into your class account. Here is how to do so from a command shell:
[xyz.ece.lsu.edu]% cd ~ Change to your home directory. /home/classes/ee4720/ee472000 [xyz.ece.lsu.edu]% cp -r /home/faculty/koppel/pub/ee4720/hw/2022/hw01 .

Don't miss the dot at the end of the command. This copies the hw01 directory into your class account. You should know how to browse the files in the directory, edit, copy, delete them, etc. This may be a good time to practice your Unix shell (command-line interface) skills.
Change to the homework assignment directory.
[xyz.ece.lsu.edu]% cd ~/hw01 Change to directory HOME/hw01. /home/classes/ee4720/ee472000/hw01
Verify that files were copied, and look at what's there.
[xyz.ece.lsu.edu]% ls -la List directory, long format, show all files. total 24 drwxr-xr-x 2 ee472000 ad4720 4096 Jan 17 12:22 . drwxr-x--- 5 ee472000 ad4720 4096 Jan 17 12:22 .. -rw-r--r-- 1 ee472000 ad4720 5937 Jan 17 12:22 hw01.s

Your directory listing may contain a different collection of files, but there should be one of the form hw0X.s.
Load the homework assignment into an Emacs buffer. From the shell:
[xyz.ece.lsu.edu]% cd ~/hw01 This command is only needed if you changed directories since the last steps. [xyz.ece.lsu.edu]% emacs hw01.s & Start Emacs in background, have it load hw01.s.

There is no need to exit Emacs until you are done. Emacs may start showing two panes, with the assignment in the upper pane and "Welcome to GNU Emacs.." in the lower pane. If so, and if you'd like to hide the welcome message place the cursor in the upper pane and enter the key sequence Ctrlx 1 or for those preferring to use the WIMP interface select Remove Other Windows from the File menu.
Verify that Emacs is working correctly.
If Emacs has been set up properly you should see comments in red and the text LSU EE 4720 should appear in a black bold sans-serif font.
Verify that the MIPS simulator is working: Press F9 to start the MIPS simulator graphically using the file in the current buffer as an input. To start the simulator non-graphically press Ctrl-F9.
If started graphically, a window should pop up labeled xspim, with a primitive graphical user interface. It started non-graphically a pane should have opened with a (spim) prompt.
Read the instructions in the file.
The comments in file hw01.s either describe the homework problem or provide a link to the problems. Edit hw01.s to complete the assignment. Please just modify one file, unless instructions in the assignment code or the handout indicate that additional files should be modified.
Solve the problems.
An exact sequence of commands cannot be provided for this step.
The assignment will automatically be copied at the due date, usually close to midnight or in the early morning on the day after the due date. A trial copy may be performed before the due date and a warning E-mail will be sent if the file could not be found.

Using SPIM (Spring 2024)

Background

SPIM is a simple MIPS simulator. It reads MIPS assembly language programs, then assembles and executes them. The version of SPIM used here is slightly modified from the original but the original documentation should be useful. The classroom assignment will not run on the original version. SPIM can run graphically or non-graphically. If can be run within Emacs (recommended) or from the command line.

Getting Started

These steps show how to run a MIPS program on SPIM. After completing these steps look at the Basic Skills section to learn techniques useful for debugging. SPIM can be used graphically or non-graphically. The instructions below show how to load and run the assignment with Emacs, a text editor. Text editors other than Emacs can be used, such as Vim. If you are using Emacs (recommended) skip the instructions for starting SPIM from the command line. If you are using some other text editor skip the instructions for starting Emacs and for starting SPIM within Emacs.

Follow the account setup instructions and log into your account.
Familiarize yourself with Emacs by following the Using Emacs to Edit a File instructions.
Load a MIPS assembler file into an Emacs buffer, perhaps by following the Homework Flow instructions above:
[xyz.ece.lsu.edu]% cd ~/hw01 Change to directory HOME/hw01. /home/classes/ee4720/ee47201234/hw01 [xyz.ece.lsu.edu]% emacs hw01.s Start Emacs using hw01.s as first file to edit.

An Emacs window should open up with an assembler file loaded. If setup was performed correctly then LSU EE 4720 should appear in a black bold font. If not, re-try the setup or ask for help.
Start SPIM graphically within Emacs by pressing F9.
A window entitled xspim should pop up. The top pane should show register values, the next pane should have buttons, the third should show the program in binary and assembler forms, the fourth pane shows the data area, and the bottom pane (which might extend past the bottom of the screen) shows messages.
Start SPIM graphically from the command line by typing:
[xyz.ece.lsu.edu]% cd ~/hw01 Change to directory HOME/hw01. /home/classes/ee4720/ee47201234/hw01 [xyz.ece.lsu.edu]% hw-xspim hw01.s Start SPIM graphically loading the code in hw01.s.

A window entitled xspim should pop up. The contents of this window is described in Start SPIM graphically within Emacs step above.
Start SPIM non-graphically within Emacs by pressing Ctrl-F9.
A pane (window in Emacs parlance) should open up showing a SPIM banner, brief help, and a prompt.
SPIM Version 6.3.1 lsu of 9 November 2001, 17:34:35 CST LSU Version Date: 2022-01-31 Copyright 1990-2000 by James R. Larus (larus@cs.wisc.edu). All Rights Reserved. See the file README for a full copyright notice. Includes LSU modifications. File loaded. Type "run" to run normally. Type "step 100" to execute next 100 instructions with tracing. Type "help" for more help. (spim)
Start SPIM non-graphically from the command line by typing:
[xyz.ece.lsu.edu]% cd ~/hw01 Change to directory HOME/hw01. /home/classes/ee4720/ee47201234/hw01 [xyz.ece.lsu.edu]% hw-spim hw01.s Start SPIM non-graphically loading the code in hw01.s. SPIM Version 6.3.1 lsu of 9 November 2001, 17:34:35 CST LSU Version Date: 2022-01-31 Copyright 1990-2000 by James R. Larus (larus@cs.wisc.edu). All Rights Reserved. See the file README for a full copyright notice. Includes LSU modifications. File loaded. Type "run" to run normally. Type "step 100" to execute next 100 instructions with tracing. Type "help" for more help. (spim)

To return control to the command line type quit at the (spim) prompt.
Check for error messages. When running graphically the error messages will appear in the bottom-most pane. It may be necessary to make other panes smaller to see the bottommost pane. If there are any errors fix them, exit the simulator and restart.
Run the program graphically by clicking the run button then clicking ok on the dialog box that pops up.
If the program generates output (and EE 4720 assignments do, at least if they run long enough) a window entitled SPIM Console should pop up. If you don't see it try moving the simulator window. To scroll the SPIM Console window first focus it (by clicking on it) and then use the arrow keys to scroll.
Run the program non-graphically by entering the command run and pressing Enter.
(spim) run ** Starting Test of Routine "strlen_p1 (Problem 1 - Bit Ops)" ** String 1: Length 1 is correct. Took 10 insn or 0.100 char/insn String 2: Length 2 is correct. Took 13 insn or 0.154 char/insn String 3: Length 3 is correct. Took 16 insn or 0.188 char/insn String 4: Length 4 is correct. Took 19 insn or 0.211 char/insn String 5: Length 5 is correct. Took 22 insn or 0.227 char/insn String 6: Length 0 is correct. Took 7 insn or 0.000 char/insn String 7: Length 23 is correct. Took 76 insn or 0.303 char/insn String 8: Length 196 is correct. Took 595 insn or 0.329 char/insn (spim)

The output above is a shortned version of 2022 Homework 1 output.
If you're satisfied with the output then you're done, otherwise edit the MIPS program and try again. See the Basic Skills section for some debugging techniques.

Basic Debugging Skills

Students should have the following basic debugging skills before attempting a homework assignment. More realistically, students should remember that these basic debugging skills are conveniently described here so that they can review them after encountering problems in an initial attempt to solve the homework.

Single-Step Execution
Do this by clicking step in the main SPIM window then clicking step in the small dialog that pops up. Each press of step will advance execution by one instruction, this can be seen by the movement of highlighting in the Text Segments pane.
Determine Register and Memory Values
For those who might not have noticed, the top of the main SPIM window shows register values. Memory values are shown in the Data Segments pane. To find the address of the data you are interested find a la pseudo-instruction that loads the address of that data.
Set a Breakpoint
Single-stepping is a pain if you need to execute hundreds of instructions before execution reaches the instruction you're interested in. If this applies to you, find the address of the instruction by scrolling the Text Segments pane until your instruction is visible; the address is the first hexadecimal number. Then select breakpoints and enter the address.
Find Documentation
Many errors are due to the incorrect usage of an instruction. Looking up an instruction should be quick and easy, so set a bookmark on your favorite browser or otherwise provide one-click access to the instruction documentation

Generating an Excution Trace (For Debugging)

An execution trace of a program execution (trace for short) is a record of which instructions executed and what they did. It is often helpful for debugging, especially for short assembly routines. SPIM generates a trace when run non-graphically using the step command.

Load assembly code into an Emacs buffer in a properly set up account.
Start SPIM non-graphically by pressing Ctrl-F9.
SPIM Version 6.3.1 lsu of 9 November 2001, 17:34:35 CST LSU Version Date: 2022-01-31 Copyright 1990-2000 by James R. Larus (larus@cs.wisc.edu). All Rights Reserved. See the file README for a full copyright notice. Includes LSU modifications. File loaded. Type "run" to run normally. Type "step 100" to execute next 100 instructions with tracing. Type "help" for more help. (spim)
Tell SPIM to execute enough instructions to reach the part of your code experiencing the problem. Assume that 100 instructions is enough.
(spim) step 100 [0x00400064] 0x4080b000 mtc0 $0, $22 ; 220: mtc0 $0, $22 Insn Exec ** Starting Test of Routine "strlen_p1 (Problem 1 - Bit Ops)" ** Prog Output [0x004000d0] 0x0100f809 jalr $31, $8 ; 253: jalr $t0 Insn Exec # Change in $31 ($ra) 0x4000bc -> 0x4000d8 Decimal: 4194492 -> 4194520 Reg Change

Some of the output is shown above. That output includes the execution trace mixed with program output. The program output is the line containing Starting Test of. The lines starting with square brackets, such as [0x004000d0], show an instruction that executed. The lines starting with # Change in show changed register values.
Instruction Execution Description
[0x00400000] 0x20820000 addi $2, $4, 0 ; 84: addi $v0, $a0, 0 Instruction Encoded Disassembled Line Insn as written Address Insn Instruction No. in source file

The line above provides information about an instruction that executed. The number in the square brackets, 0x00400000, is the address (PC) of the instruction. The instruction itself is shown in three forms. The easiest to understand form is the way it appeared in the input file, that is shown after the semicolon. Immediately after the semicolon is a line number, 84, followed by the instruction.
The instruction is shown in encoded form after its address. Above the encoded form is 0x20820000. Finally, the instruction is shown disassembled, that's addi $2, $4, 0 above. The disassembled form is obtained from the encoded form. Register numbers are used instead of names. If the assembler file used a pseudoinstruction then the disassembled form would show the actual instruction. Since addi is not a pseudoinstruction the two are the same.
Register Change Description
[0x00400000] 0x20820000 addi $2, $4, 0 ; 84: addi $v0, $a0, 0 # Change in $2 ($v0) 0xffffffff -> 0x10010000 Decimal: -1 -> 268500992

The line above shows an instruction execution followed by information about a register that it wrote. The instruction writes register $2 also known as $v0. The value changes from -1 to 268500992. Note that the values are shown both in hexadecimal and decimal.

Common SPIM Problems

The following problems are frequently encountered when using SPIM.

Can't scroll SPIM windows.
To scroll the SPIM console window and the panes in the main SPIM window first focus by clicking in the window or pane, and then use the up or down arrow keys.
SPIM Does Not Start After Pressing F9 in Emacs
Make sure the file has a name that ends .s. If so Assembler should appear in the mode line near the bottom of the Emacs window. If Assembler appears, check for a SPIM pull-down menu. If not, double-check the account setup instructions. Make sure your system has an X server. If so, Emacs will appear in its own window, not in a terminal program (such as ssh or telnet). If all the preceding is okay and SPIM still doesn't run Emacs probably can't find the xspim program. You might be running on the wrong system (should be ECE Sun or Linux systems) or else something has changed. (If it's the year 2030 things might have been moved without updating these instructions.)
Syntax and Other Assembly Errors
When you start SPIM look for errors on the bottommost pane. That pane should start SPIM Version 6.3.1... If there are no errors it should end See the file README for a full copyright notice.
Program Does not Seem to Run
In the run or step dialog the staring address should be about 0x00400000. If the starting address is zero then SPIM could not find the __start symbol that should appear before the routine that is to run first. If you are trying to run a homework solution shell make sure you haven't deleted any code or that there are no errors that are confusing SPIM before it reaches __start.
Stack Overflow Error
Most likely due to an infinite recursion error. A recursive procedure needs to test some kind of no-more-recursion condition before making a recursive call. If this condition is always false then recursion will be infinite and stack space will be exhausted.
Address Errors
A zero or other invalid address is often due to common programming errors, such as never setting a register to an address in the first place. A misaligned address occurs when a lw or sw instruction is executed with an address that's not a multiple of 4, or for lh, etc., a multiple of 2.

Common MIPS Errors

The following are common errors in MIPS programs.

Unintended Instruction in Delay Slot

#
# Example Error:
#
    addi $a0, $a0, 4
    j SOMEWHERE

    # Okay, here I do something else.
ELSEWHERE:
   add $a0, $t0, $s1

#
# Code with Error Fixed:
#
    addi $a0, $a0, 4
    j SOMEWHERE
    nop              # Later I'll find something useful to put here.

    # Okay, here I do something else.
ELSEWHERE:
   add $a0, $t0, $s1

In the first code fragment above the add $a0, $t0, $s1 is executed even though the jump is taken.

Wrong Data Type Size

#
# Example Error
  lw $t0, 0($a0)
  addi $a0, $a0, 1
  lw $t1, 0($a0)

# Correct Code
  lw $t0, 0($a0)
  addi $a0, $a0, 4
  lw $t1, 0($a0)

Program Does Not Work Properly, For Some Reason
To debug a program find the point at which it stops doing what was intended. To do this you need to know what the program should be doing, so review the algorithm and work out a bit by hand. You should also be able to single step, set SPIM breakpoints, and examine register and memory values. Simple errors can be caught by reviewing the code, but in more complex programs there is no substitute for watching what happens when it runs.

Running PSE (Updated Spring 2008)

Use PSE to view a dataset file on the ECE Linux or Sun Systems

The procedure below is for viewing a dataset file using PSE. The procedure uses the sample dataset file perl.ds. For an assignment substitute the appropriate file.

Log in to your account.
Use any valid ECE Sun or Linux account, a class account does not have to be used.
Make sure that PSE (and other programs used for classes) is in your execution path. One way is to follow the class account setup instructions. Otherwise put the following in your .bashrc file, or set the execution path and optionally PSE_DIR as shown:
if [ `uname` == 'Linux' ]; then export PATH=/home/faculty/koppel/pub/ee4720/lbin:$PATH else export PATH=/home/faculty/koppel/pub/ee4720/bin:$PATH export LD_LIBRARY_PATH=/usr/lib:/usr/openwin/lib:/usr/dt/lib:/opt/local/lib:$LD_LIBRARY_PATH fi export PSE_DIR=/home/faculty/koppel/pub/ee4720/ds
Start a shell. For example by right-clicking the desktop and selecting "Open Terminal."
Enter the command:
pse &

A window titled "No Dataset - PSE" should pop up. If the account was not set up properly the shell might give the error pse: Command not found.. If so, setup the account or type /home/faculty/koppel/pub/ee4720/lbin/pse (on Linux) or /home/faculty/koppel/pub/ee4720/bin/pse (on Suns) instead of just pse.
The ampersand after pse runs it in the background so you can use the shell for other commands, for example, running PSE on a different dataset.
Select Open from the File menu. An Open File dialog should pop up. If the dataset file to open (perl.ds, for example) is visible click on it, otherwise either navigate to the directory containing the file, type a path in the File text entry box, or call over a classmate and ask "should it be doing this?"
If all goes well PSE should pop up a progress bar then show a window full of dots (the overview window).
If the account was set up properly PSE should look for files in the class dataset directory, /home/faculty/koppel/pub/ee4720/ds. This default dataset directory is determined by environment variable PSE_DIR.
Initially PSE displays an overview of execution, with black dots showing IPC (instructions per cycle) over a segment of program execution. Other color dots may also be shown, click the "+" on the left hand side to add more (or use the View | Overview Plot Series Choose menu). The status line along the bottom shows time (in cycles), an instruction number (based on a count of committed instructions), and a tag (based on a count of decoded instructions).
Move the cursor over an interesting point and clock to view details.
The display should switch to a pipeline execution diagram (PED) plot. Use the Overview button to return to the overview window.
To change the view between a ROB to a PED (pipeline execution diagram) press the PED button.
Though they look very different, a PED plot is an upside down and rearranged ROB plot, as can be seen by paying close attention to the animation.
There is no way to close the current dataset or load a second one. (It's on the to-do list.) Run PSE again to view another dataset file. Note that by running PSE in the background its easy to start multiple, simultaneous sessions.
Read the PSE documentation.
For those who just can't right now, here are some useful key bindings:
Left and Right Arrow: Scroll through the ROB or PED plot.
Home and End: Go to the beginning or end or ROB or PED plot.
See the View menu for zoom command key bindings.
Beware.
Clip mode prevents instructions from wrapping from bottom to top in PED plots. When turned on it may make a bad choice about which instructions to show. If you think that's happening make sure the clip button is out.
If the Unlock button is visible that means the instructions shown by the disassembly window won't follow the cursor. If that's what you want, fine, otherwise press unlock.

Emacs Text Editor (Fall 2016)

Background

Emacs, at its core, is a text editor, however surrounding that core are many commands and modes to help with programming tasks of all kinds and other activities from the practical, such as editing files on remote computers (look for Remote Files in the documentation), to the amusing, such as inserting keywords designed to attract the attention of counterespionage agents (M-x spook). Emacs has commands for practically anything.

Using Emacs to Edit a File

These steps show how to use Emacs to edit a file. The first step shows how to start Emacs graphically, which is what you'd want to do if you were not connecting remotely. Connecting non-graphically is the better option if you were connecting remotely (say from your PC at home).

To run Emacs graphically type emacs & in a command shell or start using the Applications | Accessories | Emacs Text Editor menu items.
A window should pop up, the frame will be labeled Emacs.
To run Emacs non-graphically type emacs -nw in a command shell.
Emacs should start, there should be a character-mode menu across the top.
Load a file by selecting Open File... from the Files menu. If running non-graphically press F10 to access the menus.
Enter a file name. Note that text may appear in the bottom of the main window in an area called the minibuffer, or in a dialog box. (Once loaded, the file name will appear in the mode line near the bottom of the window.)
Enter text in the buffer to try out the editor.
Select Save Buffer from the Files menu to save.
When done with editing for the day select Exit Emacs from Files to exit.
Many users prefer to leave Emacs open with multiple files rather than exiting and re-starting Emacs for each file edited.

Running the Emacs Tutorial

The tutorial is an introduction for first-time users.

Start emacs.
Select Emacs Tutorial from the Help menu. Do not attempt to learn everything the first day.

Starting Info, Emacs' Help

Info provides detailed documentation for Emacs and other programs.

Start Emacs
Select Browse Manuals from Help menu.
Following instructions, select the Emacs manual.

EE 4720 - Procedures

Contents

Account Setup (Updated Spring 2022)

To Setup Account for use with SPIM, PSE and Other Software

Remote Access to Workstation Lab

MIPS Homework and Practice Work Flow (Spring 2022)

Basic Steps

Using SPIM (Spring 2024)

Background

Getting Started

Basic Debugging Skills

Generating an Excution Trace (For Debugging)

Common SPIM Problems

Common MIPS Errors

Running PSE (Updated Spring 2008)

Use PSE to view a dataset file on the ECE Linux or Sun Systems

Emacs Text Editor (Fall 2016)

Background

Using Emacs to Edit a File

Running the Emacs Tutorial

Starting Info, Emacs' Help

Account Setup (Updated Spring 2022)

To Setup Account for use with SPIM, PSE and Other Software

MIPS Homework and Practice Work Flow (Spring 2022)

Basic Steps

Using SPIM (Spring 2024)

Background

Getting Started

Basic Debugging Skills

Generating an Excution Trace (For Debugging)

Common SPIM Problems

Common MIPS Errors

Running PSE (Updated Spring 2008)

Use PSE to view a dataset file on the ECE Linux or Sun Systems

Emacs Text Editor (Fall 2016)

Background

Using Emacs to Edit a File

Running the Emacs Tutorial

Starting Info, Emacs' Help

David M. Koppelman - koppel@ece.lsu.edu	Modified 5 Feb 2024 17:57 (2357 UTC)
Provide Website Feedback • Accessibility Statement • Privacy Statement