Page 1 of 1

Tracking gzdoom.ini with a version control system

PostPosted: Sat Aug 01, 2020 1:29 pm
by SP_FACE1
Do you keep track of the changes to your GZDooM related configuration files? If so, how?

Recently I added `gzdoom.ini` to my "dotfiles", i.e. started tracking it with Git. It works but it is somewhat annoying when every time I launch GZDooM it changes some lines even though I don't explicitly change anything. Should I add my changes to `autoexec.cfg` and only track that? How are people usually doing this?

Re: Tracking gzdoom.ini with a version control system

PostPosted: Tue Aug 04, 2020 1:11 pm
by wolfmanfp
If I were to create a dotfiles repo, I would only track autoexec.cfg, since gzdoom.ini is overwritten at every launch (correct me if I'm wrong though).

Re: Tracking gzdoom.ini with a version control system

PostPosted: Thu Aug 06, 2020 1:39 am
by Graf Zahl
Yes, it is, the file is generally unsuitable for being tracked.

Re: Tracking gzdoom.ini with a version control system

PostPosted: Thu Aug 06, 2020 8:16 am
by JPL
I have one in-progress project that uses an INI to track certain settings and the only thing that changes from run to run is the first line in the file that logs the time of last run. It's annoying but not a huge deal. Very few reasons to track it though outside the weird specific stuff my project is doing.
I use an Autoexec.cfg for my preferred settings for actually playing GZDoom.

Re: Tracking gzdoom.ini with a version control system

PostPosted: Thu Aug 06, 2020 5:48 pm
by SP_FACE1
Thanks for the replies. I'm migrating to autoexec.cfg now.

How can I set the IWAD search path and the file search path via autoexec.cfg?

(In the .ini file they are both set with `Path` but under a different [subsection].)