Vi IMproved--Vim and Happy Hacking Keyboard Lite 2
When you type vi on most Linux boxes, you're likely to get Vim. This is a good thing, but until now nobody has written a book that covers the features Vim has over vi.
Steve Oualline to the rescue. Some readers wrote in to say that Steve changed their lives with his article "That's Vimprovement! A Better vi" in our February issue. It's wonderful to be a part of bringing such a wonderful transformation to you people, and Steve's new book brings even more Vim knowledge to the masses.
Thank the book gods that it didn't come bundled with a CD-ROM. I hope this is a trend--book publishers should stop including software that will probably be obsolete for most of the book's shelf life. If this book should be bundled with anything, it's the new Happy Hacking Keyboard Lite 2 from PFU America. We used the QWERTY version, but there are also Dvorak and Japanese versions.
Vim enhances the original vi so you can edit faster, but the Happy Hacking series of keyboards removes features to achieve the same goal. There's no top row of function keys or anything right of Enter. Escape moves down to just left of the number one, which is why we're mentioning this keyboard in an review of a book about Vim--there'll be no more "Mom, can you make me some sandwiches? I'm going to go hit Escape today, be back for dinner." The missing keys are available with Fn, so you can still do a SysRq if you need to.
The Control key is where it belongs, above the left Shift. And the upper right corner is a little changed from a standard PC keyboard too. A DIP-switchable backspace/delete key is above Enter, and backslash/pipe and tilde/backquote are above that.
The Happy Hacking Keyboard Lite 2 adds cursor keys in an inverted T below the right Shift key. Fans of the original Happy Hacking Keyboard, which Linux Journal reviewed in 1998, will notice one other change--there's now a second Fn key on the left, so you can use both Fn and the left "diamond" (no Windows logo, but it acts like it) key.
Speaking of Fn keys, Fn works flawlessly with any other combination of modifiers, so if you have enough fingers you can still switch virtual consoles. Three-key combinations like Ctrl-Alt-F1 become four-key combinations like Ctrl-Alt-Fn-1. Set your fireworks on the ground before you light them and you should be OK.
How well does it work? The small size and small lip on the front increase the perceived height--because it's smaller, it feels thicker. If you use a wrist rest you might want to experiment with different ones. The key feel doesn't have the classic feel of increased resistance, then a spring click, then less resistance, as in an old IBM keyboard. The keys aren't completely mushy like a cheap PC keyboard, though. The closest I can come to describing the feel is that it's like a high-quality laptop keyboard but with much longer key travel.
The big question of course is can you use the Happy Hacking Keyboard and switch back to a regular keyboard for occasional edits without going insane? In my experience, yes.
Until your Happy Hacking Keyboard comes, if you're using a regular keyboard with Vim, you might want to stick "imap <F1> <esc>" in your .vimrc, to keep from hitting F1 for help when all you want to do is hit escape.
That brings us to the subject of .vimrc files. Do a Google search for "my .vimrc" and you will get hundreds of them--all full of productivity-maximizing, carpal-tunnel-saving goodness. Or, depending on your point of view, productivity-sucking days of tweaking your .vimrc just right so that when you do write something it will be really easy to do.
Even if you visit vim.org daily and are always working on your .virmrc to incorporate stuff you get off the Net, Steve's book makes a great command reference. One nice touch is that the reference appendices, which list commands in alphabetical order, include page numbers for those commands that are explained in detail in the body of the book.
If you're new to Vim, or to vi-like editors in general, the tutorial at the beginning of the book looks good and quickly transitions from a basic survival guide to true power editing. For basic wrist health reasons, it's a good idea to pick up as much text editing skill as possible, and carrying around a copy of this book is a great way to do it. If you just know enough vi to get by, you're leaving all the power of Vim on the table and needlessly trashing your wrists.
For example, if you've ever had unexpected results when pasting text into Vim from an X application, then :set paste will make the pasted-in text come out a lot closer to the original than it might otherwise. Commands and configuration settings abound.
There's also a detailed "Cookbook" chapter where you can find recipes for dealing with a lot of common editing tasks. Except where he has to, Steve keeps everything organized in short sections that you can read and apply quickly. The state of my .vimrc is much improved since the day I picked up this book.
As you might expect from the author of Practical C Programming, there is a lot of good information on how to customize Vim to handle C and other programming languages. Steve covers indentation, syntax highlighting and automatically dealing with make and the compiler in great detail. For example, you can insert a "modeline" in a file to enforce your tab settings even when someone with a differently configured Vim edits it. And Vim will run make for you, then automatically open any files with errors for editing.
There are no entries in the index for "mail" or "e-mail" and little information about how to use Vim for nonprogramming tasks like dealing with quoted text in e-mail. If you're searching for customization tweaks to make Vim do what you want as a mail editor, you might have to wait for a good book on Mutt.
There's excellent coverage of Vim's own built-in scripting language, but no examples of using Python or Perl, with which Vim can be integrated.
At no point does this book bother to say anything about which features are found in the original vi and which are Vim innovations. If you learn Vim, then log in to some legacy UNIX box, you'd better grab a copy of Vim. Fortunately, Vim is insanely portable, even to non-UNIX-like OSes, and there's an appendix that covers installation. So if you're spoiled by Vim and can never go back to regular vi, there's still hope for you.
Don Marti is the technical editor for Linux Journal. He can be reached at firstname.lastname@example.org.
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|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Google's SwiftShader Released
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 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