#SingleInstance why not make it the default Topic is solved

[cgx5871]

#SingleInstance why not make it the default
Every script must write this line.
Most people are used to running on a single instance, right?

[andymbody]

I assume you mean #SingleInstance, force

If so... Agreed!!

[cgx5871]

I assume you mean #SingleInstance, force

If so... Agreed!!

If the parameter is omitted, it defaults to Force

[andymbody]

If the parameter is omitted, it defaults to Force

Ok... that must have changed in v2. V1 defaults to "prompt" (as far as I know)

[swagfag]

good point, why not. makes u wonder why this wasnt the default behavior in the first place

In this version, by default, multiple instances of the same script can be launched. If you wish to limit a script to a single instance, use the #SingleInstance directive described below.

---

#SingleInstance: Specifying this anywhere in a script will prevent new instances of that script from being launched once there is already one running. Instead, you will be prompted for whether to close the existing instance. Note: You do not need to use "on" or "off" with this command.

Improved the behavior of #SingleInstance scripts when the user attempts to run another instance: The user is now prompted for whether to keep the original instance or replace it with the new one.

Improved #SingleInstance with an optional FORCE parameter that skips the warning dialog. [thanks beardboy]

Improved #SingleInstance to optionally ignore attempts to launch a script that is already running. [thanks Rajat]

Changed scripts that use hotkeys, hotstrings, or #Persistent so that #SingleInstance is automatically implied. Use #SingleInstance Off to override this.

(Might break existing scripts): Scripts that contain the GUI command anywhere are automatically single-instance unless the #SingleInstance directive has been used to override that. In addition, GUI scripts are now instantly persistent rather than becoming so only after a GUI window is created.

[xMaxrayx]

Meh disagree if you are using a lot of libraries and shared Ahk processes, this won't be good, besides we now need to re-write all theses old scripts

You can make Auto-apply snippet in (vs code) when you are creating a new Ahk file (write whatever you want as defoult.

You can use AHK++ it has that future.

[niCode]

Meh disagree if you are using a lot of libraries and shared Ahk processes

I don't know what libraries has anything to do with the topic and I'm not sure what you mean by scripts "sharing" a process. Could you elaborate?

I have actually never heard of someone that intentionally runs multiple of the same script, or read about someone suggesting to do that to solve a particular problem. The lack of info on multiple instances in a practical scenario means I'm not even sure what the benefit would be. I'm sure scenarios exist but it feels like they would be so rare that the default should absolutely be #SingleInstance, Force because that's how the overwhelming majority of people use their scripts and it also avoids confusion for new people if they accidentally run multiple of the same script and inevitably have issues.

[Marium0505]

@niCode
Many use cases where you would have more than one instance of a script running at the same time, let's say the script is a calculator, I sometimes have multiple calculators open at the same time, and don't get me started on browsers... Or windows explorer windows.... or VS Code windows.

[niCode]

Those are all programs, not scripts. If you were making a point, it didn't come across.