From: Richard Levitte <richard@levitte.org>
Date: Mon, 22 Feb 2021 05:08:55 +0000 (+0100)
Subject: Always cNORM before "\n"
X-Git-Tag: v3.0.0~34
X-Git-Url: http://wagner.pp.ru/gitweb/?a=commitdiff_plain;h=b56b7ee05276b92c282efa412ae94163b88ec350;hp=b56b7ee05276b92c282efa412ae94163b88ec350;p=openssl-gost%2Fengine.git

Always cNORM before "\n"

Using cNORM after "\n" may or may not work, probably because of the
line buffered nature of standard output.

If an error is displayed immediately after a printf that has cNORM
after "\n", the error output sometimes "overrides" the cNORM, and you
may end up with a surprisingly colorful error message, not to mention
that this may also affect your prompt in the same manner.

The lesson is to always output cNORM before the ending "\n".
---