Single script to run in both Windows batch and Linux Bash?

by

What I have done is use cmd’s label syntax as comment marker. The label character, a colon (:), is equivalent to true in most POSIXish shells. If you immediately follow the label character by another character which can’t be used in a GOTO, then commenting your cmd script should not affect your cmd code.

The hack is to put lines of code after the character sequence “:;”. If you’re writing mostly one-liner scripts or, as may be the case, can write one line of sh for many lines of cmd, the following might be fine. Don’t forget that any use of $? must be before your next colon : because : resets $? to 0.

:; echo "Hi, I’m ${SHELL}."; exit $?
@ECHO OFF
ECHO I'm %COMSPEC%

A very contrived example of guarding $?:

:; false; ret=$?
:; [ ${ret} = 0 ] || { echo "Program failed with code ${ret}." >&2; exit 1; }
:; exit
ECHO CMD code.

Another idea for skipping over cmd code is to use heredocs so that sh treats the cmd code as an unused string and cmd interprets it. In this case, we make sure that our heredoc’s delimiter is both quoted (to stop sh from doing any sort of interpretation on its contents when running with sh) and starts with : so that cmd skips over it like any other line starting with :.

:; echo "I am ${SHELL}"
:<<"::CMDLITERAL"
ECHO I am %COMSPEC%
::CMDLITERAL
:; echo "And ${SHELL} is back!"
:; exit
ECHO And back to %COMSPEC%

Depending on your needs or coding style, interlacing cmd and sh code may or may not make sense. Using heredocs is one method to perform such interlacing. This could, however, be extended with the GOTO technique:

:<<"::CMDLITERAL"
@ECHO OFF
GOTO :CMDSCRIPT
::CMDLITERAL

echo "I can write free-form ${SHELL} now!"
if :; then
  echo "This makes conditional constructs so much easier because"
  echo "they can now span multiple lines."
fi
exit $?

:CMDSCRIPT
ECHO Welcome to %COMSPEC%

Universal comments, of course, can be done with the character sequence : # or :;#. The space or semicolon are necessary because sh considers # to be part of a command name if it is not the first character of an identifier. For example, you might want to write universal comments in the first lines of your file before using the GOTO method to split your code. Then you can inform your reader of why your script is written so oddly:

: # This is a special script which intermixes both sh
: # and cmd code. It is written this way because it is
: # used in system() shell-outs directly in otherwise
: # portable code. See https://stackoverflow.com/questions/17510688
: # for details.
:; echo "This is ${SHELL}"; exit
@ECHO OFF
ECHO This is %COMSPEC%

Thus, some ideas and ways to accomplish sh and cmd-compatible scripts without serious side effects as far as I know (and without having cmd output '#' is not recognized as an internal or external command, operable program or batch file.).

More Related Contents:

  1. Make Bash handle variables like Batch
  2. Batch equivalent of Bash backticks
  3. How to mount a host directory in a Docker container
  4. Why equal to operator does not work if it is surrounded by space?
  5. Brace expansion with a Bash variable – {0..$foo}
  6. “~/Desktop/test.txt: No such file or directory”
  7. Associative arrays: error “declare: -A: invalid option”
  8. Capturing Groups From a Grep RegEx
  9. Jq to replace text directly on file (like sed -i)
  10. Integer ASCII value to character in BASH using printf
  11. How do I get the directory where a Bash script is located from within the script itself?
  12. Bash: Syntax error: redirection unexpected
  13. Use Bash to read line by line and keep space
  14. How to increment version number in a shell script?
  15. Get just the filename from a path in a Bash script [duplicate]
  16. if, elif, else statement issues in Bash
  17. Is there a way to make bash job control quiet?
  18. How to store the output of a command in a variable at the same time as printing the output?
  19. Why is bash errexit not behaving as expected in function calls?
  20. How do file descriptors work?
  21. bash script loop through two variables in lock step
  22. Check if a file is executable
  23. When does command substitution spawn more subshells than the same commands in isolation?
  24. Rsync syntax error when run from bash script
  25. How do I get both STDOUT and STDERR to go to the terminal and a log file?
  26. -bash: __git_ps1: command not found
  27. Retry a Bash command with timeout
  28. How to append a string at end of a specific line in a file in bash [duplicate]
  29. docker entrypoint running bash script gets “permission denied”
  30. What does `kill -0 $pid` in a shell script do?

Leave a Comment