+logfile

[NeoHippo]

In my autoexec.cfg I have this line,
logfile startup.txt

While GZDoom creates a logfile startup.txt, which includes the Date and Time in the file, ie:
Log started: Wed Nov 04 09:35:40 2009
it overwrites the old file with a new one every time that GZDoom is started.

Could it be done a la Skulltag, which adds the Date and Time to the logfile name, ie:
startup.txt__2009_11_04-10_40_02.log
and thusly creates a next logfile every time, leaving the old file(s) intact ?

[Sussudio]

Good idea.

[Enjay]

Oh dear lord please no! I'm sick of hundreds of files piling up on my HD because of Skulltag doing that without (as far as I can tell) an option to switch off log files. It also dumps them in my root directory which I really don't like.

I too usually start GZdoom with a logfile but I'm absolutely fine with it over-writing the previous one.

I suppose a compromise would be to allow a naming system but include some kind of limit to the number of files GZdoom writes?

[Sussudio]

It should be optional of course, for testing purposes.

[Enjay]

+logfile is already optional (which is more than the SkullTag version seems to be ). Perhaps some kind of setting to allow multiple (renamed) logfiles or something?

[Sussudio]

Yep, that's what I was talking about.

[NeoHippo]

I suppose a compromise would be to allow a naming system but include some kind of limit to the number of files GZdoom writes?

Maybe ten would be enough to satisfy even a rigorous testing session.

[Gez]

Keep logfile working as it does now. Please.

However, I'd be okay with a new, different, separate command that would work like Skulltag does. Let's say "dlogfile", with a "d" for "dated".

This way everybody should be happy, both those who want to keep all logs and those who want to have it constantly overwritten.

[Graf Zahl]

Wow, some people surely can't be bothered to think for even a second, can they?

Request denied.