Sublime Forum

Build behaviour difference ST3 - ST4

#1

Dearest Forum,

By switching from ST3 to ST4 I noticed a small change in the behaviour of how successive builds are executed. In ST4 executing a new build closes the old instance of the build if I hit ctrl+b multiple times. This is different (atleast in my installation) in ST3 where multiple successive builds would pop up if I execute a build multiple items using ctrl+b.
I did like to get the old behavior back as it was pretty convenient e.g. when i am working with matplotlib python scripts. Does somebody know whether there is a setting that can do this in ST4?

0 Likes
#2

It sounds like what you’re describing is the current build being stopped before a new one is started?

The exec command that’s used to carry out builds by default now allows build systems to include a kill_previous key that tells it to kill the prior running build before starting the current build, but it’s set to false by default which should behave the same as ST3 in this case.

What does your sublime-build file look like? It might also be an idea to see if the same thing happens in Safe Mode.

0 Likes
#3

ST4 sets kill_previous to true by default.

1 Like
#4

Hi,
adding "kill_previous":false to my build system returned the old behaviour. Thanks! Using the safe mode didnt work.

For completeness my full build system now look like this:
{
“cmd”: [“python3”, “-u”, “$file”],
“file_regex”: “^[ ]File "(…?)”, line ([0-9]*)",
“selector”: “source.python”,
“kill_previous”: false
}

0 Likes