From d9fa2fd38959b65f50baa3000ccfdcc0312f0ff7 Mon Sep 17 00:00:00 2001 From: Carlo von lynX Date: Tue, 9 Aug 2016 10:00:29 +0000 Subject: [PATCH] end-user friendly output messages, ok like this? --- src/util/common_logging.c | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/src/util/common_logging.c b/src/util/common_logging.c index ecbe69443..a391d0b9e 100644 --- a/src/util/common_logging.c +++ b/src/util/common_logging.c @@ -801,12 +801,26 @@ output_message (enum GNUNET_ErrorType kind, if ( (NULL != GNUNET_stderr) && (NULL == loggers) ) { - FPRINTF (GNUNET_stderr, + if (kind == GNUNET_ERROR_TYPE_MESSAGE) { + /* The idea here is to produce "normal" output messages + * for end users while still having the power of the + * logging engine for developer needs. So ideally this + * is what it should look like when CLI tools are used + * interactively, yet the same message shouldn't look + * this way if the output is going to logfiles or robots + * instead. Is this the right place to do this? --lynX + */ + FPRINTF (GNUNET_stderr, + "* %s", + msg); + } else { + FPRINTF (GNUNET_stderr, "%s %s %s %s", datestr, comp, GNUNET_error_type_to_string (kind), msg); + } fflush (GNUNET_stderr); } pos = loggers; -- 2.25.1