path: root/doc/README.follow
diff options
authorSteve Slaven <bpk@hoopajoo.net>2019-11-05 06:26:14 (GMT)
committerSteve Slaven <bpk@hoopajoo.net>2019-11-05 06:26:14 (GMT)
commit9c4c0a1e366b9d932e4ab2ce03a0e80126d93d9b (patch)
tree928e4c6f49ac50f7e69777b00073df37d7d11e3f /doc/README.follow
parenteb9898c7fcc017a35c240c1bd83c8a8ff451431a (diff)
reorganizing files
Diffstat (limited to 'doc/README.follow')
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/README.follow b/doc/README.follow
new file mode 100644
index 0000000..9ef923b
--- /dev/null
+++ b/doc/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