git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[RFC PATCH 3/2] vreportf: add prefix to each line

From
Jeff King <peff@peff.net>
Date
Jan 11, 2017, 14:07 UTC
Message-ID
<20170111140758.yyfsc3r3spqpi6es@sigill.intra.peff.net>
In-Reply-To
<20170111140138.5p647xuqpqrej63b@sigill.intra.peff.net>
On Wed, Jan 11, 2017 at 09:01:38AM -0500, Jeff King wrote:
>   [1/2]: Revert "vreportf: avoid intermediate buffer"
>   [2/2]: vreport: sanitize ASCII control chars

We've talked before about repeating the "error:" header for multi-line messages. The reversion in patch 1 makes this easy to play with, so I did. I kind of hate it. But here it is, for your viewing pleasure.

-- >8 --
Subject: vreportf: add prefix to each line

Some error and warning messages are multi-line, but we put the prefix only on the first line. This means that either the subsequent lines don't have any indication that they're connected to the original error, or the caller has to make multiple calls to error() or warning(). And that's not even possible for die().

Instead, let's put the prefix at the start of each line, just as advise() does.

Note that this patch doesn't update the tests yet, so it causes tons of failures. This is just to see what it might look like.

It's actually kind of ugly. For instance, a failing test in t3600 now produces:

   error: the following files have staged content different from both the
   error: file and the HEAD:
   error:     bar.txt
   error:     foo.txt
   error: (use -f to force removal)

which seems a bit aggressive. It also screws up messages which indent with tabs (the prefix eats up some of the tabstop, making the indentation smaller). And the result is a little harder if you need to cut-and-paste the file lines (if your terminal lets you triple-click to select a whole line, now you have this "error:" cruft on the front).

It may be possible to address some of that by using some other kind of continuation marker (instead of just repeating the prefix), and expanding initial tabs.

Signed-off-by: Jeff King <peff@peff.net>
---
 usage.c | 16 ++++++++++++++--
 1 file changed, 14 insertions(+), 2 deletions(-)
diff --git a/usage.c b/usage.c
index ad6d2910f..8a1f6ff4e 100644
--- a/usage.c
+++ b/usage.c
@@ -8,18 +8,30 @@
 
 static FILE *error_handle;
 
+static void show_line(FILE *fh, const char *prefix, const char *line, int len)
+{
+	fprintf(fh, "%s%.*s\n", prefix, len, line);
+}
+
 void vreportf(const char *prefix, const char *err, va_list params)
 {
 	char msg[4096];
 	FILE *fh = error_handle ? error_handle : stderr;
+	const char *base;
 	char *p;
 
 	vsnprintf(msg, sizeof(msg), err, params);
+
+	base = msg;
 	for (p = msg; *p; p++) {
-		if (iscntrl(*p) && *p != '\t' && *p != '\n')
+		if (*p == '\n') {
+			show_line(fh, prefix, base, p - base);
+			base = p + 1;
+		} else if (iscntrl(*p) && *p != '\t')
 			*p = '?';
 	}
-	fprintf(fh, "%s%s\n", prefix, msg);
+
+	show_line(fh, prefix, base, p - base);
 }
 
 static NORETURN void usage_builtin(const char *err, va_list params)
-- 
2.11.0.627.gfa6151259
Previous: Jeff KingNext: Junio C Hamano
Message 4 of 6 in “sanitizing error message contents”
  1. 0/2 sanitizing error message contentsJeff King, Jan 11, 2017
  2. 1/2 Revert "vreportf: avoid intermediate buffer"Jeff King, Jan 11, 2017
  3. 2/2 vreport: sanitize ASCII control charsJeff King, Jan 11, 2017
  4. 3/2 vreportf: add prefix to each lineJeff King, Jan 11, 2017
  5. Junio C HamanoJan 11, 2017
  6. Jeff KingJan 12, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.