diff options
| author | Steve Slaven <bpk@hoopajoo.net> | 2005-03-21 18:40:47 (GMT) |
|---|---|---|
| committer | Steve Slaven <bpk@hoopajoo.net> | 2005-03-21 18:40:47 (GMT) |
| commit | cb2555e19237930a25989a7cd2bee4589f1d515d (patch) | |
| tree | 524bf902278ca892821a6be886ac3b51cfa9910f /README.follow | |
| parent | 22e2e8b44054a4e95dd473079f0e7800284b0d20 (diff) | |
| download | powwow-cb2555e19237930a25989a7cd2bee4589f1d515d.zip powwow-cb2555e19237930a25989a7cd2bee4589f1d515d.tar.gz powwow-cb2555e19237930a25989a7cd2bee4589f1d515d.tar.bz2 | |
Convert all `' to "" as per the powwow-1.2.6-dain patch. Note I did not apply
the patch since 1.2.7 has some differences to 1.2.5 with regard to command
handling and things, so I'm applying the diff parts by hand mostly
Diffstat (limited to 'README.follow')
| -rw-r--r-- | README.follow | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/README.follow b/README.follow index 8b4e185..9ef923b 100644 --- a/README.follow +++ b/README.follow @@ -3,15 +3,15 @@ This mini-program is mainly intended for debugging powwow. It is completely standalone, and needs to be called with a file-name -(example: `follow mycapture'). -Hitting ESC or ^C quits `follow', hitting RETURN prints the next line +(example: "follow mycapture"). +Hitting ESC or ^C quits "follow", hitting RETURN prints the next line of the file, any other key prints the next character (only one) of the file I know it is a _stupid_ program, but it is useful if you find screen-related bugs in powwow, i.e. powwow does not print some lines or prints something wrong. In that case, if you redirect powwow output to a file and reproduce the bug, -you can use `follow your-filename' to examine the file and see what is wrong +you can use "follow your-filename" to examine the file and see what is wrong How to send a copy of powwow output to a file: powwow your-arguments | tee your-filename |