Set DEFAULT_PRE_STRING to red.

[coloredstderr/coloredstderr.git] / README

diff --git a/README b/README
index 298ce4ff3c6346ce373afcf2bb421fc77dd588ea..a99edfa3f2952a79f07a2dc519de87c57055f7d7 100644 (file)
--- a/README
+++ b/README
@@ -6,6 +6,8 @@ coloredstderr is a small library which uses 'LD_PRELOAD' to color stderr.
 
 Like all solutions using 'LD_PRELOAD' it only works with dynamically linked
 binaries. Statically linked binaries, for example valgrind, are not supported.
+setuid binaries are also not supported ('LD_PRELOAD' disabled for security
+reasons).
 
 
 It was inspired by stderred [2]. Similar solutions (using 'LD_PRELOAD')
@@ -83,8 +85,7 @@ A default setup could look like this:
 The following additional environment variables are available:
 
 - 'COLORED_STDERR_PRE'
-  String to write before each write to stderr, defaults to "\033[91m" (bright
-  red).
+  String to write before each write to stderr, defaults to "\033[31m" (red).
 - 'COLORED_STDERR_POST'
   String to write after each write to stderr, defaults to "\033[0m" (reset
   color).
@@ -93,6 +94,10 @@ The following additional environment variables are available:
   terminal, e.g. when writing to a file. By default, only writes to a terminal
   are colored.
 
+All environment variables starting with 'COLORED_STDERR_PRIVATE_*' are
+internal variables used by the implementation and should not be set manually.
+See the source for details.
+
 
 To set custom colors as pre/post strings you can use the `$''` feature of Bash
 and Zsh:
@@ -131,6 +136,14 @@ doesn't exist it's created. An existing file isn't overwritten, but the
 warnings are appended at the end.
 
 
+KNOWN ISSUES
+------------
+
+- `{fputc,putc,putchar}_unlocked()` are not hooked when writing to stdout
+  (which might be redirected to stderr). Can't be fixed as the compiler
+  inlines the code into the program without calling any function.
+
+
 BUGS
 ----