Even if Lister is configured for Autodetection of Font at startup this is seen with the new use of parameters for em_Listhistory.txt wrote: 24.05.22 Added: The internal commands cm_list, cm_listInternalOnly, cm_listInternalMulti, cm_listOnly, cm_listMulti now support the same parameters as via command line, with switch / at the start, e.g. cm_list /T1 filename (32/64)
24.05.22 Added: Command line parameter /S=L to open a separate Lister window: New sub-parameter F to open Lister in full screen view, e.g. /S=L:F filename (32/64)
If I use for example this command line:
%COMMANDER_EXE% /S=L:T1
Lister start up in ANSI mode, just if I just use cm_List
But if I use cm_List /S=L:T1
Lister starts up in ASCII mode - and worse - any use of cm_list (without parameters) or F3 thereafter starts in ASCII mode until I restart TC.
This applies to T1-T8 ,N,A,S and P parameters. If I use the V parameter, every following use of cm_list (without parameters) or F3 results in Variable char width to be used until I restart TC.
If I override the Autodetection of Font at startup by usinf for example cm_List /S=L:AT1 - things work OK, but of course without autodetection.
EDIT:
My mistake!
If I omit /S=L: and just use for example cm_List /T1 instead of cm_List /S=L:T1 things work OK - but since the history says: " now support the same parameters as via command line" I expected /S=L:T1 to work as well - it would be conveniant if it did work too - especially since it almost does work, except for the font problem.