for %%a in (*) do start "" "%%a"

[Contro]

What exactly does this line of batch code ? :

for %%a in (*) do start "" "%%a"


I don't recommend to use.
Collapse two times my system.

[lujomu]

It launches EVERY file and folder in the current directory.
I.e. it runs every executable or script files, opens every other file in its respective app and opens an explorer window for every folder.

A little trick to identify what a loop actually does is to insert the word "echo" after "do". This will print out each command instead of executing it:

Code

for %%a in (*) do echo start "" "%%a"

Hope that helps!

[KynloStephen66515]

What exactly does this line of batch code ? :

for %%a in (*) do start "" "%%a"


I don't recommend to use.
Collapse two times my system.

So you ran a batch file that you didn't have clue what it did?    Seems like a totally reasonable and safe things to do...lmao

[Contro]

It launches EVERY file and folder in the current directory.
I.e. it runs every executable or script files, opens every other file in its respective app and opens an explorer window for every folder.

A little trick to identify what a loop actually does is to insert the word "echo" after "do". This will print out each command instead of executing it:

Code

for %%a in (*) do echo start "" "%%a"

Hope that helps!

But really don't go.
I try and collapse also with an execution from a folder containing eight urls and collapsed.

[Contro]

Ejem I tried because comes in a forum for years i use, but not always

What exactly does this line of batch code ? :

for %%a in (*) do start "" "%%a"


I don't recommend to use.
Collapse two times my system.

So you ran a batch file that you didn't have clue what it did?    Seems like a totally reasonable and safe things to do...lmao

I try because was posted in a forum i visit several years ago....

[Edvard]

The best advice ever when running random code posted in a forum, is exactly as Stephen alluded to:
NEVER run code that you don't know what it is going to do.  Perhaps you wanted to run this script because you saw it as a batch-bomb of sorts, and wanted to look into how to prevent it from crashing your system.  But not knowing?... just don't do it.

For example, DON'T run this:

Code

 :s
 start "" %0
 goto s

or this:

Code

%0|%0

until you know what it does, and how to stop it.  And now that you've seen the code, you'll be able to spot it in the wild.
You're welcome.

[Vurbal]

The best advice ever when running random code posted in a forum, is exactly as Stephen alluded to:
NEVER run code that you don't know what it is going to do.  Perhaps you wanted to run this script because you saw it as a batch-bomb of sorts, and wanted to look into how to prevent it from crashing your system.  But not knowing?... just don't do it.

At the very least run it in a vm. I can understand if you're the type of person who needs to see something in action to understand it. Given that it's both easy and free to do it safely, when somebody who ought to know better chooses to play Russian roulette, I have to think they're getting what they deserve.