Merge branch 'release-4.16.1'

[i3/i3] / man / i3-dump-log.man

diff --git a/man/i3-dump-log.man b/man/i3-dump-log.man
index 8e9094ff0078c285954eb03d38b628e2f58ce920..455144071c0d81a6322a0a3386ffeb1d786e23ec 100644 (file)
--- a/man/i3-dump-log.man
+++ b/man/i3-dump-log.man
@@ -1,7 +1,7 @@
 i3-dump-log(1)
 ==============
-Michael Stapelberg <michael+i3@stapelberg.de>
-v4.1, December 2011
+Michael Stapelberg <michael@i3wm.org>
+v4.6, September 2013
 
 == NAME
 
@@ -9,16 +9,19 @@ i3-dump-log - dumps the i3 SHM log
 
 == SYNOPSIS
 
-i3-dump-log [-s <socketpath>]
+i3-dump-log [-s <socketpath>] [-f]
 
 == DESCRIPTION
 
 Debug versions of i3 automatically use 1% of your RAM (but 25 MiB max) to store
-full debug loglevel log output. This is extremely helpful for bugreports and
+full debug log output. This is extremely helpful for bugreports and
 figuring out what is going on, without permanently logging to a file.
 
 With i3-dump-log, you can dump the SHM log to stdout.
 
+The -f flag works like tail -f, i.e. the process does not terminate after
+dumping the log, but prints new lines as they appear.
+
 == EXAMPLE
 
 i3-dump-log | gzip -9 > /tmp/i3-log.gz