CLI generates incorrect gcode

Describe the bug When slicing an STL model using batch mode, the gcode produced is different from the gcode produced using the GUI and is incorrect. Specifically, the bed temperature is not set until after the filament gcode, meaning the heated bed is not heated until after the object has been printed.

To Reproduce Steps to reproduce the behavior:

1. Export gcode for attached model in GUI
2. Gcode exported is in "footbridge-N-c.gui.gcode"
3. Run "slic3r --no-gui $f --load pla-creality.ini --bed-temperature 45"
4. Gcode produced by CLI is in "footbridge-N-c.cli.gcode"
5. Note the position of the M140 command in both files - in the gui file, it is at the very beginning of the file. In the cli file, it is at the end (and thus not in effect during the printing of the model)

Expected behavior Gcode exported by the gUI and by the CLI should be identical given identical option selections

Desktop (please complete the following information):

• OS: Linux
• Version 1.3.0 bed-temp-bug.zip

I have also encountered in version 1.3.0 that setting the bed temperature does not work. Im on Debian and I used slic3r on the command line since the GUI did not work at all.