path: root/README.follow
diff options
authorSteve Slaven <bpk@hoopajoo.net>2005-03-12 00:27:55 (GMT)
committerSteve Slaven <bpk@hoopajoo.net>2005-03-12 00:27:55 (GMT)
commit77b250bfb63a28a8fe8a8da67de7354bce6e61ff (patch)
treee28f72c18305016c19c608f5fce4432529e7673d /README.follow
parent5dfb1906b299bf7c8a1ee3ba5cd1c9ea40648d89 (diff)
Initial revisionv1.2.7
Diffstat (limited to 'README.follow')
1 files changed, 18 insertions, 0 deletions
diff --git a/README.follow b/README.follow
new file mode 100644
index 0000000..8b4e185
--- /dev/null
+++ b/README.follow
@@ -0,0 +1,18 @@
+ follow 0.1 README
+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
+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
+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
+How to send a copy of powwow output to a file:
+powwow your-arguments | tee your-filename