Leon

I can prevent capturing in the CI runs with `-s` however this makes `--log-cli-level` become useless.

For now I have switched to a more defensive set of options that won't print above WARNING level by default: ``` def pytest_configure(config): # Make sure --log-cli-level can be used...

After restarting/rebooting various environments the behaviouor has changed once again. I now have live logs but some of them are formatted incorrectly, and without the `-s` flag I get all...

Final comment: I note that `pytest` itself fails its test suite when I use the `-s` command line option: ``` FAILED testing/test_config.py::TestDebugOptions::test_debug_help - Failed: nomatch: '*Store internal tracing debug information...

Just adding my 2c. Agree with @HPLegion in general, custom log levels seem to be discouraged in the logging module docs. One thing I note is that numba is "special"...

Based on a quick perusal of the code, I see the most obvious candidates for slow functions in [`update_highlight`] and [`get_window_info`], both of which are called on `WinEnter` via `source_win_enter`....

Aha, I believe the issues I'm observing depend on filetypes. The slowdown when switching windows is only really noticable when I'm switching to special buffers like an empty buffer from...

I have updated the video which shows that swapping to a `help` buffer is faster than swapping to an empty buffer and the highlight issue. I was navigating splits with...

I'd also be happy with just a keybinding for reloading the file for starters.

Thanks for looking at this, the downloader I used to get these was a matlab shear-wave splitting plugin. However, I was using an older version (of both Matlab and the...