Instructions: Use the commands that you learned in class to find answers to these questions. Don't use a search engine like Google, and don't ask your neighbor. If you need a hint, ask the TA. When you find a new command, run it so you can see exactly how it works. In addition to turning in the answers to these questions, turn in a description of your session discovering them. As you do actions, use a Linux-based editor to record your keystrokes and each answer in files key1.txt and ans1.txt that you will submit as part of the assignment.
How can you get man to print all the commands that have a specific word in their man page (or at least the description part of the man page)? (hint: man man)
Where are the cp and wc programs located in the file system?
What executable programs have names that are just one character long, and what do they do?
When you execute the command named by the symbolic link /usr/bin/cc, which file actually is executed?
The chmod program changes permissions on a file. What does the symbolic mode g-s mean, in terms of permissions?
What option to find lets you search for files that have been modified in the last 3 days?
Use the previous answer to find all directories modified in the last 3 days.
Of the files in the same directory as find, how many of them are symbolic links?
What is the oldest regular file in the /usr/lib directory?
Where does the locale command get its data from?
In Emacs, what commands have sort in their name?
Briefly, what do the Emacs keystrokes C-a through C-z do? Can you list their actions concisely?
In more detail, what does the Emacs keystroke C-g do?
What does the Emacs yank function do?
When looking at the directory /usr/bin, what's the difference between the output of the ls -l command, and the directory listing of the Emacs dired command?
Homework: Learning to use Emacs
Keith Waclena, A Tutorial Introduction to GNU Emacs (2009)
The Emacs editor (2015)
An Introduction to Programming in Emacs Lisp (2015)
For all the exercises, record the steps taken to accomplish the given tasks. Use intelligent ways of answering the questions. For example, if asked to move to the first occurrence of the word "scrumptious", do not merely use cursor keys to move the cursor by hand; instead, use the builtin search capabilities to find "scrumptious" quickly.
To start, download a copy of the web page you're looking at into a file named assign1.html. You can do this with Wget or cURL. Use cp to make three copies of this file. Call the copies exer1.html, exer2.html, and exer3.html.
Exercise 1.1: Moving around in Emacs
Use Emacs to edit the file exer1.html.
Move the cursor to somewhere in the first line that contains the text "ASCII".
Move the cursor to somewhere in the first line that contains the text "Instructions".
Move the cursor to the first letter of first occurrence of the word "HTML".
Move the cursor to the first letter of first occurrence of the word "hunt".
Move the cursor to the end of the current line.
Move the cursor to the beginning of the current line.
Move the cursor back to somewhere in the first line of the file.
Have you been moving the cursor using the arrow keys? If so, repeat the above, without using the arrow keys.
Doing the above tasks with the arrow keys takes many keystrokes, or it involves holding down keys for a long time. Can you think of a way to do it with fewer keystrokes by using some of the commands available in Emacs?
When you are done, exit Emacs.
Exercise 1.2: Deleting text in Emacs
Use Emacs to edit the file exer2.html. The idea is to delete its HTML comments; the resulting page should display the same text as the original.
Delete the 18th line, which is an HTML comment. <!-- HTML comments look like this. --
Delete the HTML comment containing the text "DELETEME DELETEME DELETEME".
Delete the HTML comment containing the text "http://en.wikipedia.org/wiki/HTML_comment#Comments".
There's one more HTML comment; delete that one too.
Once again, try to accomplish the tasks using a small number of keystrokes. When you are done, save the file and exit back to the command line. You can check your work by using a browser to view exer2.html. Also, check that you haven't deleted something that you want to keep, by using the following command:
diff -u exer1.html exer2.html exer2.diff
The output file exer2.diff should describe only text that you wanted to remove. Don't remove exer2.diff; you'll need it later.
Exercise 1.3: Inserting text in Emacs
Use Emacs to edit the file exer3.html.
Change the first two instances of "Assignment 1" to "Assignment 37".
Change the first instance of "UTF-8" to "US-ASCII".
Insert a blank line after the first line containing "<ol".
When you finish, save the text file and exit Emacs. As before, use the diff command to check your work.
Exercise 1.4: Other editing tasks in Emacs
In addition to inserting and deleting text, there are other common tasks that you should know, like copy and paste, search and replace, and undo.
Execute the command "cat exer2.html exer2.diff exer4.html" to create a file exer4.html that contains a copy of exer2.html followed by a copy of exer2.diff.
Use Emacs to edit the file exer4.html. The idea is to edit the file so that it looks identical to exer1.html on a browser, but the file itself is a little bit different internally.
Go to the end of the file. Copy the new lines in the last chunk of diff output, and paste them into the correct location earlier in the file.
Repeat the process, until the earlier part of the file is identical to what was in the original.
Delete the last part of the file, which contains the diff output.
… except we didn't really want to do that, so undo the deletion.
Turn the diff output into a comment, by surrounding it with "<!--" and "--".
Now let's try some search and replaces. Search the text document for the pattern "<ol". How many instances did you find? Use the search and replace function to replace them all with the initial-caps equivalent "<Ol".
Check your work with viewing exer4.html with an HTML browser, and by running the shell command "diff -u exer1.html exer4.html exer4.diff". The only differences should be changes from "<ol" to "<Ol", and a long HTML comment at the end.
Exercise 1.5: Doing commands in Emacs
Do these tasks all within Emacs. Don't use a shell subcommand if you can avoid it.
Create a new directory junk that's right under your home directory.
In that directory, create a C source file hello.c that contains the following text. Take care to get the text exactly right, with no trailing spaces or empty lines, with the initial # in the leftmost column of the first line, and with all other lines indented to match exactly as shown:#include <stdio.h
int
main (void)
{
char n = '\n';
char b = '\\';
char q = '"';
char const *p = "#include <stdio.h%cint%cmain (void)%c{%c char n = '%cn';%c char b = '%c%c';%c char q = '%c';%c char const *p = %c%s%c;%c printf (p, n, n, n, n, b, n, b, b, n, q, n, q, p, q, n, n, n, n);%c return 0;%c}%c";
printf (p, n, n, n, n, b, n, b, b, n, q, n, q, p, q, n, n, n, n);
return 0;
}
Compile this file, using the Emacs compile command.
Run the compiled program, and put its output into a new Emacs buffer named hello-out.
Copy this buffer's contents directly into the log that you're maintaining for this exercise. (You are using Emacs to maintain the log, aren't you?)
Exercise 1.6: Running Elisp code
Visit Emacs's *scratch* buffer.
In the buffer, compute a random integer by invoking the random function. Use C-j (eval-print-last-sexp) to invoke the random function.
In the buffer, assign three random integers to the global variables x, y and z. You can start by executing (setq x (random)). Again, use C-j.
What is the product of the three variables? You can find this out by executing (* x y z). What do you observe about the result? If the answer seems to be the correct mathematical answer, try again with a different set of random integers.
Try evaluating (* x y z) again, but this time with M-: (eval-expression). What difference do you observe in the output?
Are the random integers truly random in the mathematical sense? If not, what's not random about them?
Submit
Submit the following files.
key1.txt
For each homework exercise, the set of keystrokes needed to do the exercise. Attempt to use as few keystrokes as possible. Do not bother to write down the keystrokes needed to start the editor (e.g., e m a c s SP e x e r 1 . h t m l Enter) or to type in the complicated C program of Exercise 1.5. Write down the label of the key for each keystroke, e.g., "a", "A" (if you type "a" while holding down the shift key), "Tab", "Enter", "Esc". Use SP for space. Use prefix "C-" and "M-" for control and meta characters: e.g., C-f represents Control-F, and M-f represents Meta-F. Put a space between each pair of keystroke representations. For example: e m a c s < v i Backspace Backspace Backspace v i. If you use some key not described above, invent your own ASCII name for the key and explain what key you mean, but don't put spaces in your key name.
ans1.txt
Answers to each lab question, along with a very brief description of how you can easily find such the answer from a new Ubuntu system, the next time you need the answer.
The .txt files should be ASCII text files, with no carriage returns, and with no more than 80 columns per line except when logging program output longer than that. The shell command:
awk '/\r/ || 80 < length' key1.txt ans1.txt
should output only a small number of log lines.
25