Midnight Commander feels very sluggish under the built-in terminal

[ghost]

I tried --nosubshell, but it didn’t help.

Another issue: It doesn’t always happen, but sometimes when you use F4 to edit a file and exit with F10, upon returning to the main UI of Midnight Commander you can still see fragments of the file content.

I asked Copilot and it listed common issues with ncurses buffers:

• Dirty buffer / fragments left behind: If parts of the screen aren’t cleared properly, you may see leftover text (like what you described in Midnight Commander).

• Forgetting to clear windows: Developers often need to call clear(), erase(), or wclear(win) before redrawing.

• Not refreshing: If you update the buffer but don’t call refresh(), changes won’t appear.

• Terminal quirks: Some terminals (like xterm) may behave differently, especially with alternate screen buffers.

Well, I think it’s a terminal quirk, because I haven’t experienced a similar problem on other terminal emulators.

[SpartanJ]

Yes, this happens when there's no proper invalidation of the line buffers, MC is pretty old, it might do something uncommon, it might behave weirdly on Windows (I can confirm this does not happen to me on Linux), IDK, I haven't seen the issue beside some rare case, not particularly relevant. It's also not slow at all to me, so yeah, there must be something fishy on the Windows side.