Shell Escapes: Running One UnixCommand While Using Another (Unix Power Tools, 3rd Edition)

start page | rating of books | rating of authors | reviews | copyrights

17.21. Shell Escapes: Running One UnixCommand While Using Another

Some Unix commands (usually interactive commands like vi) let you run another Unix command temporarily. To do that, you type a special command character -- usually an exclamation point (!) -- then type the Unix command line you want to run. In this article, I'll show examples for the vi editor. To see if this works on another utility, check its documentation or just try typing !Unixcommand when the utility is waiting for you to type a command.

You can run any Unix command without quitting vi. That's handy, for example, if you want to read your mail or look at some other file . . . , then go back to the file you were editing without losing your place. It's called a "shell escape." (By the way, there's a another way to do this, job control (Section 23.3), that works on most Unix systems. Job control is often more convenient and flexible than shell escapes.)

Let's say you're editing the file named foo and you need to run grep to get someone's phone number from your phone file. The steps are as follows:

Be sure you're in command mode (press the ESC key if you aren't sure).
If you want to run a command that needs the file you're editing, remember to write out your vi buffer with the :w command. (So you probably wouldn't need to write anything before the following grep command.) Type :! followed by the Unix command, then press RETURN. For example:
```
:!grep tim ~/phone
```
The grep program will run. When it finishes, vi will say:
```
[Hit return to continue]
```
After you press RETURN, you'll be right back where you were.

Other examples:

:!less afile: Page through afile on your screen.
:!rcsdiff %: Give this file to the rcsdiff (Section 11.3) program to see what you've changed since the file was checked out of the archive. vi replaces % with the name of the file you're editing now (Section 17.3).
:!mail: Read your mail. Be careful about this if you were already running the mail program and you used the command ~v to edit a message with vi from inside the mail program. This shell escape starts a subshell (Section 24.4); it will not take you back to the same mail session before you started editing!
:sh: Start a completely new shell. (If you are using a shell with job control, you'll almost always want to use job control to suspend vi temporarily instead (Section 23.6). Press CTRL-z, or use the ex command :suspend.)

Basically, anything you can do at a shell prompt, you can do with a shell escape. You'll be in a subshell though, not your original login shell. So commands like cd won't affect the program where you started the subshell or any other shell. On the bright side, changing directories or resetting anything in your environment won't affect vi or the shell where you started vi. Terminating the program you're running in the subshell will bring you right back where you were.

-- JP


17.20. Be Careful with vi -r Recovered Buffers		17.22. vi Compound Searches