I have a Batch script I essentially want it to present the user with a notepad window opened with a configuration file for the user to edit each time they run the script, and I want the Command Prompt to wait until this program is closed to continue with execution, and run the program that uses this configuration file.
I want to do this because I don't want to take user input in the Batch script with the "set /P" command style, and have to set-up parsing reading and writing to that configuration file that has many values to inspect.
I believe the standard behavior on Windows when executing any executable program, is for "exe" files it will open the program in its own process and immediately control back to the script/command prompt. For "bat" and "cmd" script files, it will execute the script and wait until control is passed back to the first script or command prompt. This should be the behavior when at least calling the other script with the "CALL" command or calling it directly.
Now on Linux I believe the default behavior for executable content that is both native machine code that can come without an extension, and scripts like "sh" files, are executed in a blocking manner, unless you specify the ampersand ("&") character somewhere on the input line.
So I am trying to achieve the blocking behavior on Windows as it is more easily accomplished on Linux, and would like the closing of the program to trigger the original script to continue, or return control to the command prompt.