Add workaround for endless loop of WinCMD script

[stkevintan]

I just set up the CMD auto run script in my windows machine (Windows 11 Enterprise, 23H2, x64)
I firstly encountered %i was unexpected at this time., so I changed to script the Cmder version (double the %)
after that, the cmd hangs forever, and a huge amount of cmd process emerged:

I got the answer from https://stackoverflow.com/a/57451662

The problem is, FOR /F starts a new instace of cmd.exe and that instance also starts your auto run script, this can result into an endless loop.

So I updated the README, hope my experience can help other peopoe

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5b921ea

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Schniz]

i trust you that it works, but it makes the readme very busy with wincmd stuff that I'm not entirely sure people are still using today. maybe we should add a docs/wincmd.md page? maybe we should change the wincmd initialization script?

[Schniz]

I believe it was addressed in a different PR. Thank you for the contribution