Why Use a Command Line Instead of a GUI?
These are the slides for my talk on
8 May 2001 at Oregon State University.
This talk is similar to
my 1999 talk for SVLUG,
but I've made some updates.
Summary: As Linux gets GUI-er, you might be surprised at
how much faster and more powerful the plain old command line (with
a % or $ prompt) can be in many cases.
When should you type instead of clicking?
Note: the slides are formatted for a Web browser 800 pixels wide
by 600 pixels high.
Another note: If you look inside the HTML files ("view source"),
there are HTML comments with extra information for my talk.
Look for <!-- at the left margin.
You can get all these slides as a gzipped tar-format archive:
osu_20010508.tar.gz.
- Why Use a Command Line Instead of a GUI? (Intro)
- Jerry Peek
- Overview
- Main Issues
- Shells Handle Command Lines
- History Substitutions: Overview
- History Substitution: Examples #1
- History Substitution: Examples #2
- String Expansion (Curly Braces)
- Command Substitution
- Perl/etc. on the Command Line
- Shell Variables, Loops
- UNIX Filters and Pipes
- Shell Scripts, Aliases, Functions
- Email in the UNIX style: MH
- Summary
[Talks page]
[Home page]
Contact Jerry Peek