I knew similar thing happens with QuickView behavior for text view e.g. in case it can't detect ANSI or ASCII encoding, Christian Ghisler described this in email reply to one of my reports about difference of Lister and QuickView behavior:
Christian Ghisler wrote:[... if QuickView] cannot distinguish between manual OEM mode (the user has set it) and auto-detect OEM mode [...] when you switch to the next file and [QuickView] is in OEM mode, it will remain in OEM mode because it assumes that the user wants to view files in OEM mode.
I didn't expect similar behavior in QuickView exists for plugins too...
I suggest to introduce new cm_<somename> command with parameter to control QuickView behavior, and suggest at least following values for parameter:
0 - current QuickView behavior, it will decide what mode to use for text and what plugins to use in Multimedia mode.
1 - Use Lister behavior to decide what mode to use for text, but QuickView method for using plugins.
2 - Use QuickView behavior to decide what mode to use for text, but Lister method for using plugins.
3 - always use Lister's method to decide what mode to use for text and what plugins to use in Multimedia mode.
I'm talking not only about wincmd.ini parameter, but about cm_ command because QuickView is used to view many files quickly, and user may have a need to change QuickView method of work quicky without TC restart.