Re: [PATCH] Add a notice that only certain functions can print color escape codes

3 messages, 3 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH] Add a notice that only certain functions can print color escape codes

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:47:47

Johannes Sixt [off-list ref] writes:
Like this?
Yeah, and in addition to "puts", "write(2)" is also not supported, right?
quoted hunk
 color.h |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/color.h b/color.h
index 7d8da6f..edeaa3e 100644
--- a/color.h
+++ b/color.h
@@ -4,6 +4,11 @@
 /* "\033[1;38;5;2xx;48;5;2xxm\0" is 23 bytes */
 #define COLOR_MAXLEN 24

+/*
+ * IMPORTANT: Due to the way these color codes are emulated on Windows,
+ * write them only using printf, fprintf, and fputs. In particular,
+ * do not use puts.
+ */
 #define GIT_COLOR_NORMAL	""
 #define GIT_COLOR_RESET		"\033[m"
 #define GIT_COLOR_BOLD		"\033[1m"
-- 
1.6.6.rc0.43.g50037

Re: [PATCH] Add a notice that only certain functions can print color escape codes

From: Johannes Sixt <hidden>
Date: 2016-06-15 22:47:47

Junio C Hamano schrieb:
Johannes Sixt [off-list ref] writes:
quoted
Like this?
Yeah, and in addition to "puts", "write(2)" is also not supported, right?
Correct, good catch!
--- 8< ---
From: Johannes Sixt <redacted>
Subject: [PATCH] Add a notice that only certain functions can print color escape codes

We emulate color escape codes on Windows by overriding printf, fprintf,
and fputs. Warn users that these are the only functions that can be used
to print them.

Signed-off-by: Johannes Sixt <redacted>
---
 color.h |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/color.h b/color.h
index 7d8da6f..3cb4b7f 100644
--- a/color.h
+++ b/color.h
@@ -4,6 +4,11 @@
 /* "\033[1;38;5;2xx;48;5;2xxm\0" is 23 bytes */
 #define COLOR_MAXLEN 24

+/*
+ * IMPORTANT: Due to the way these color codes are emulated on Windows,
+ * write them only using printf(), fprintf(), and fputs(). In particular,
+ * do not use puts() or write().
+ */
 #define GIT_COLOR_NORMAL	""
 #define GIT_COLOR_RESET		"\033[m"
 #define GIT_COLOR_BOLD		"\033[1m"
-- 
1.6.6.rc0.43.g50037

Re: [PATCH] Add a notice that only certain functions can print color escape codes

From: Michael J Gruber <hidden>
Date: 2016-06-15 22:47:47

Johannes Sixt venit, vidit, dixit 27.11.2009 08:42:
quoted hunk
Junio C Hamano schrieb:
quoted
Johannes Sixt [off-list ref] writes:
quoted
Like this?
Yeah, and in addition to "puts", "write(2)" is also not supported, right?
Correct, good catch!
--- 8< ---
From: Johannes Sixt <redacted>
Subject: [PATCH] Add a notice that only certain functions can print color escape codes

We emulate color escape codes on Windows by overriding printf, fprintf,
and fputs. Warn users that these are the only functions that can be used
to print them.

Signed-off-by: Johannes Sixt <redacted>
---
 color.h |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/color.h b/color.h
index 7d8da6f..3cb4b7f 100644
--- a/color.h
+++ b/color.h
@@ -4,6 +4,11 @@
 /* "\033[1;38;5;2xx;48;5;2xxm\0" is 23 bytes */
 #define COLOR_MAXLEN 24

+/*
+ * IMPORTANT: Due to the way these color codes are emulated on Windows,
+ * write them only using printf(), fprintf(), and fputs(). In particular,
+ * do not use puts() or write().
Nor putchar nor putc... but they're part of the puts family, of course.
More worthwhile then listing those negatives could be a hint on another
positive: color_fprintf and friends which are declared at the end of
color.h.
+ */
 #define GIT_COLOR_NORMAL	""
 #define GIT_COLOR_RESET		"\033[m"
 #define GIT_COLOR_BOLD		"\033[1m"
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help