- May
- 397
- 4
Hello all,
With the latest release or two, I've noticed a difference in start /wait. I have the following alias:
for %x in (c:\users\michael.d.fross\configfiles\FreeFileSync\*.ffs_gui) start /wait %x
This previously would launch one instance of FreeFileSync (the associated program) with a file in the given directory, and when I closed it, another would open until all files were processed.
However, currently all open at the same time. From what I've read from the help, I'm not sure if it's now doing what it's supposed to do or if it used to do what it was supposed to do. Running with or without "/wait" yields the same result.
Any thoughts? Has anyone else noticed this?
Thanks everyone,
Michael
With the latest release or two, I've noticed a difference in start /wait. I have the following alias:
for %x in (c:\users\michael.d.fross\configfiles\FreeFileSync\*.ffs_gui) start /wait %x
This previously would launch one instance of FreeFileSync (the associated program) with a file in the given directory, and when I closed it, another would open until all files were processed.
However, currently all open at the same time. From what I've read from the help, I'm not sure if it's now doing what it's supposed to do or if it used to do what it was supposed to do. Running with or without "/wait" yields the same result.
Any thoughts? Has anyone else noticed this?
Thanks everyone,
Michael