ISPELL: Spelling Checker
As a former Technical Editor, I know how easy it is to miss incorrect spelling when proof-reading, especially if the word “looks” right, e.g., compatability (sic). For this reason, a good spelling checker is a must. The command ispell does a good job and has special features to help it do even better. The Man page for ispell is very comprehensive, so I won't go into all its options—only my favorites.
When ispell has been invoked and it finds a misspelled word, options are displayed in one line across the bottom of the screen:
[SP] <number> R)epel A)ccept I)nsert L)ookup U)ncap Q)uit e(X)it or ? for help
All you have to do is press the space bar (accept this time only) or A (accept for rest of document) to accept the spelling as is, press I to insert the word in the dictionary, or press the appropriate number or R to replace it. The main thing to watch out for is the right time to use R. When a misspelled word is found and the spelling choices are offered, the tendency is to press R for replace and enter the number of the correct choice—doing this results in the number replacing your word. Instead, enter the number of your choice immediately, and since replace is the default, the correct spelling will replace the incorrect in the text. Use R only when a correct spelling is not offered by ispell.
Most of SSC's reference cards and command summaries use troff text formatting; other manuals use TeX. Use the option -n with troff text or -t with TeX or LaTeX, and ispell will ignore formatting commands, thereby returning fewer “misspelled” words for you to accept. While an option is not available to designate a Quark file, you can always insert the QuarkXPress formatting commands into your personal dictionary the first time they come up and not be hassled again.
In fact, the personal dictionary is probably the neatest feature of all. The very first time you select I to insert a word it doesn't recognize, ispell sets up a personal dictionary named ispell_english in your home directory. After that, any word you select will be added to this dictionary, and you will never be told it is misspelled again. This feature is particularly handy for proper names, buzz words and abbreviations unique to your business. Hashed dictionaries for other languages (that have been installed) can be specified using -d. In addition, you can set up special dictionaries for particular projects. For example, when I was editing the Java Reference Cards, I set up a special dictionary named ispell_java just for Java terms in my work directory. Afterwards, whenever I ran ispell, I specified the command line as:
ispell -n -p ./ispell_java java.troff
As a result, ispell knew class names like getFontList were spelled correctly, and that getFontlist was not. By the way, don't forget that the command line specification must include the directory of the dictionary (./ in the above example); otherwise ispell will look for it in your home directory.
Another handy feature to remember is how to check a single word instead of a complete file by using the -a option. For example, if you specify:
echo compatability | ispell -a
ispell will return the one line message:
&compatability 3 0: comparability, compatibility, computability
This message tells you “compatability” is misspelled, and gives you a list of 3 best guesses in alphabetical order. If you prefer not to have the list sorted alphabetically, use the -S option, and it will be sorted by best guess.
All in all, ispell is an effective and easy-to-use all-purpose spell checker.
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide