Good - because I have one more issue - probably why I thought the bug still persisted.Not yet because I just mentioned a few more issues.
If I make a button with either:
cm_list /T1S
or
cm_list /S=L:T1S
Then Lister opens ANSI txt files in ASCII mode as expected - but if I then close Lister and press F3 or use cm_List without any parameter then ANSI files are STILL opened in ASCII mode - the only way to make F3 use ANSI mode again is to restart TC - so what I wrote in my very first post in this thread still stands - Using the S parameter makes TC get stuck in ASCII mode - and that applies to both 32bit and 64bit TC 10.50b8.
Using either /S=L:S of just /S or /S=L also causes the problem, but not using /S=L:
In the first post it was the fact that using /S=L: in TC 10.50b7 was interpreted as using the S parameter as in /S that was the main issue - that part is fixed now - but the part where intentionally using the S (for ASCII) parameter, leaves TC stuck in ASCII mode until restarted, still persists.
Even opening a jpg file with plugin by using cm_list /S, cm_list /S=L or cm_list /S=L:S will get TC stuck in ASCII mode when afterwards opening ANSI files with F3