The log to disk loses exactly one character when the data has no spaces and the remaining of the line is just one character greater than the maximum line length

[jachguate]

The log to disk loses exactly one character when the data has no spaces and the remaining of the line is just one character greater than the maximum line length of the disk writer.

Take this example:

  DiskLogger.MaxLineSize := 39;
  jachLog.LogInfo(' 40 1234567890123456789012345678901234567890');
  jachLog.LogInfo('1234567890123456789012345678901234567890');
  jachLog.LogInfo(' 41 12345678901234567890123456789012345678901');
  jachLog.LogInfo('12345678901234567890123456789012345678901');
  jachLog.LogInfo(' 50 1234567890123456789012345678901234567890');
  jachLog.LogInfo('12345678901234567890123456789012345678901234567890');

The resulting log is:

2023-02-27 14:19:38:616 00000D00 Info   40
                                       123456789012345678901234567890123456789
2023-02-27 14:19:38:616 00000D00 Info  123456789012345678901234567890123456789
2023-02-27 14:19:38:616 00000D00 Info   41
                                       123456789012345678901234567890123456789
                                       01
2023-02-27 14:19:38:616 00000D00 Info  123456789012345678901234567890123456789
                                       01
2023-02-27 14:19:38:632 00000D00 Info   50
                                       123456789012345678901234567890123456789
                                       01234567890
2023-02-27 14:19:38:632 00000D00 Info  123456789012345678901234567890123456789
                                       01234567890

The messages including exactly 40 consecutive chars in the message lost the last '0' char. All other messages are correct.