3.24 Log file disable depends on order of arguments

[Capsaicin]

With 3.24 (and 3.23, too, I think), I noticed that if I specify the -a option before the -l option, it still logs the "optimizemode" to the log file, and then disables the logfile after that.

Great program. Can't wait for v4.

[jeroen]

Yes, the program analyses the commandline arguments one by one from left to right. It has always done it like that, it's not not new to this version. I suppose I can first scan all the arguments for a "-l" argument, and then scan again for the other arguments. Ok, I'll put it on the list. In the meantime you can get around this idiosyncracy by always putting the "-l" as the very first argument.

[ewieldra]

if i read this correct :

Logfile commandline specification must always be done before all other arguments ?

so it must be
JkDefrag.exe  -l c:\log.txt -a 7 -d 2 -q c: d:

and not

JkDefrag.exe  -a 7 -d 2 -q c: d:  -l c:\log.txt

Emiel

[jeroen]

Logfile commandline specification must always be done before all other arguments ?

It's not an absolute requirement, but it's better, yes. Since v3.17 the program will write lines to the logfile about interpreting the commandline. The "-l" argument will change the name of the logfile, but by then some lines may already have been written to the default logfile. To avoid that it should be the first argument.

[ewieldra]

Thnx

Emiel