I think I ran across a bug in a batch file because it was written with unix line endings. Is this a known problem with cmd.exe running batch files in windows?
This really isn't a "bug"... as it is by-design. Windows new-lines are defined as "\r\n" ... or a "Carriage Return" and "New Line" combination... whereas *nix flavors prefer omitting the carriage return. You should always use "\r\n" in anything in Windows where possible. Anything else may be interpreted incorrectly... and cause a great deal of unexpected results.
It seems that batch labels are skipped when
LF (Unix line-ending) is used in a
For batch files there seems no difference between unix line endings and windows line endings.
call or even the creation of linefeed variables works with both styles.
And as the batch parser removes the carriage returns directly after the percent expansion phase, they will never play a big role.