I first started using the vi editor more than ten years ago while in college. However, I only mastered the very tip of the iceberg (moving around, searching, saving, etc) and never used it as my primary editor. As I started my software development career, my interests in vi all but vanished as I generally used the text editor that was part of an integrated development environment (IDE).
Now, however, I'm experiencing a resurgence of my own interest in mastering vi for two reasons. First, I found myself having the need to traverse through server-side configuration or log files more. Vi, coupled with proven command line tools such as grep and sed, etc, is almost universally available on any server and very powerful for this need. Second, I have increasingly found that my wrist and arm feel a slight discomfort when reaching for the mouse, one of the many early warning signs of repetitive strain injuries (RSI). Using a text editor fully enabled for keyboard navigation allows me to keep my hands on the keyboard at all times, vastly improving my posture.
Now, however, I'm experiencing a resurgence of my own interest in mastering vi for two reasons. First, I found myself having the need to traverse through server-side configuration or log files more. Vi, coupled with proven command line tools such as grep and sed, etc, is almost universally available on any server and very powerful for this need. Second, I have increasingly found that my wrist and arm feel a slight discomfort when reaching for the mouse, one of the many early warning signs of repetitive strain injuries (RSI). Using a text editor fully enabled for keyboard navigation allows me to keep my hands on the keyboard at all times, vastly improving my posture.
RSS Feed