Bram Moolenaar

The implementation is a bit simplistic. I actually used this to improve the screen updating speed. But mainly on Linux, I haven't done profiling on Windows. Patches are welcome.

Since when is putting a comment before #if valid C?

Robot wrote: > @brammool: This was likely always valid C/C++, you can check yourself > with `gcc` or `g++`. The requirement seems to be the line needs to be >...

> @brammool: That was a counterexample, the bug was about this case: > > ```C++ > /**/ #ifdef POSIX > #endif > ``` > > Which isn't highlighted properly by...

The last run failed. The failure in the channel test is probably just flaky. But the failure in Test_quit_long_message() is uncommon. any idea?

Actually, I can see a problem with Test_quit_long_message(), it waits for the ruler to show up but there isn't one. I'll make a patch for that, please trigger CI when...

I guess the path is too long to fit in a line, so we get only "tes" from "testdir/Xtermdir" I made a patch for that. Test_quit_long_message() also is still failing....

The failing message test shows this in the screendump: ``` Error detected while processing command line..script /private/var/folders/b f/0cr6_1t525j9r585tdpgnv_m0000gn/T/cirrus-ci-build/src/testdir/Xtest_quit_m essage: line 1: ``` No idea what would be wrong with that...

For changing the "rows" you need to edit src/testdir/test_messages.vim. Just to see the error, won't include it.

Cirrus CI reports a problem: Error while parsing tasks: INVALID_ARGUMENT: yaml: line 44: mapping values are not allowed in this context!