[GZDoom 4.4.2] An odd problem with autoexec.cfg?

[Bodhisattva]

So, I've got this main.ini file, which I use for most of my mods, and it has $DOOMWADDIR/AUTOEXECUTABLES/autoexec.cfg as the path to its Doom.AutoExec file that contains several keybindings. It works absolutely fine.
I also have second.ini (which is a copy of the main one), which I use for one specific mod, and I've just changed its Doom.AutoExec path to $DOOMWADDIR/AUTOEXECUTABLES/autoexec2.cfg. The keybindings in this second cfg-file are different.

Now, the problem is that the game keeps using the bindings from autoexec.cfg even when I load the game with second.ini, that uses autoexec2.cfg (and thus should have different actions bound to the same keys). Am I doing something wrong here?

[Graf Zahl]

How do you define your bindings in these files? Some bind commands do not override existing bindings. Also keep in mind that bindings bind commands to keys, not keys to commands, so if config A binds a key that config B does not, that binding will persist once set.

[Bodhisattva]

I did it just like in the example from this page:

alias zoomout "fov 90; eval * $mouse_sensitivity 4.5 mouse_sensitivity; rebind zoomin"
alias zoomin "fov 20; eval / $mouse_sensitivity 4.5 mouse_sensitivity; rebind zoomout"
bind F zoomin

Both cfg-files use the same key, but have slightly different commands inside the quotation marks.

By the way, I tried solving the problem by

• deleting the old second.ini,
  making a new one from a copy of main.ini,
  putting both cfgs in $PROGDIR, and
  changing the Doom.AutoExec path to $PROGDIR/autoexec.cfg and $PROGDIR/autoexec2.cfg respectively,

and it worked. But now I don't even know which of these things actually solved the issue.