From 22bff91df973871c02acf758dd925c4c05e824c7 Mon Sep 17 00:00:00 2001 From: Yves Biener Date: Mon, 3 Mar 2025 16:33:24 +0100 Subject: [PATCH] doc: tip for looking through log files generated by `zlog` --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index fb65549..3be0eb7 100644 --- a/README.md +++ b/README.md @@ -95,6 +95,7 @@ For more details about the output customization see the configuration options of - _stderr_ (default: `true`): Print log messages to stderr. > [!CAUTION] > Currently not working as log output is not appended and only the last log message will be in the resulting log file! This is a not-yet-implemented feature of the standard library of zig! See this [issue](https://github.com/ziglang/zig/issues/14375) for more details. + > For now you should instead leave this option as it is and pipe the corresponding stderr outputs to a logfile instead. ## Tips @@ -111,3 +112,4 @@ The following list shows some tips on how to use logging more effectively. These break :port try fmt.parseInt(u16, buf[0 .. len -| 1], 10); }; ``` +- When looking through the output of the log (i.e. written to disk by `program 2> log`) the `log` file contains control code characters (*ansi*) for the colored outputs. You can still see them correctly with the following command `less -rf log`