INFO() does not print message when starting with newline

[an-ky]

Description

When using INFO() to record messages, strings starting with newline are not printed on console.
I didn't see anything about this mentioned in the docs, is this a bug or by design?

Steps to reproduce

#include <catch.hpp>

TEST_CASE("INFO surprise")
{
  SECTION("without newline")
  {
    INFO("Message without newline");
    REQUIRE(false);
  }

  SECTION("with newline")
  {
    INFO("\nMessage with newline");
    REQUIRE(false);
  }
}

Output

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
base_test.exe is a Catch v2.4.2 host application.
Run with -? for options

-------------------------------------------------------------------------------
INFO surprise
  without newline
-------------------------------------------------------------------------------
D:\Projekte\monalysis\modules\base\tests\scope_exit_test.cpp(15)
...............................................................................

D:\Projekte\monalysis\modules\base\tests\scope_exit_test.cpp(18): FAILED:
  REQUIRE( false )
with message:
  Message without newline

-------------------------------------------------------------------------------
INFO surprise
  with newline
-------------------------------------------------------------------------------
D:\Projekte\monalysis\modules\base\tests\scope_exit_test.cpp(21)
...............................................................................

D:\Projekte\monalysis\modules\base\tests\scope_exit_test.cpp(24): FAILED:
  REQUIRE( false )
with message:


===============================================================================
test cases: 1 | 1 failed
assertions: 2 | 2 failed

I'd expect that the message Message with newline also be printed.

Extra information

• Catch version: v2.4.2
• Operating System: Windows10 x64
• Compiler+version: Microsoft (R) C/C++ Optimizing Compiler Version 19.16.27023.1 for x64

[horenmar]

That is very much a (weird) bug.

[horenmar]

After further investigations, this happens only for the Console (default) reporter.

---

The problem is in TextFlow's Column::iterator::calcLength that sees the "\n" and decides that means that the message must end there...