Contents
Are there shell scripts sensitive to encoding and line endings?
DOS line endings: Bourne-Again shell script, ASCII text executable, with CRLF line terminators The GNU version of the cat utility has a -v, –show-nonprinting option that displays non-printing characters. The dos2unix utility is specifically written for converting text files between Unix, Mac and DOS line endings.
How to see the line endings in Bash?
With Windows or DOS-style line endings , each line is terminated with a Carriage Return followed by a Line Feed character. You can see this otherwise invisible character in the output of cat -v yourfile:
Where does the trailing newline Char go in shell?
The command substitution function $() (and its cousin the backtick) specifically removes trailing newlines.
How to set shellopts for DOS line endings?
If you regularly encounter shell scripts with DOS line endings and want this option to be set permanently, you could set an environment variable called SHELLOPTS (all capital letters) to include igncr. This environment variable is used by Bash to set shell options when it starts (before reading any startup files).
How to encode a file in a shell?
What you want is to encode the whole file content to desired character encoding. If it fails the desired encoding does not have map for this sequence of bytes. In shell maybe use python, perl or like Laurence Gonsalves says iconv.
How to save a file with Unix line endings?
The solution is to convert the file to use Unix-style line endings. There are a number of ways this can be accomplished: Open the file in a capable text editor (Sublime, Notepad++, not Notepad) and configure it to save files with Unix line endings, e.g., with Vim, run the following command before (re)saving:
Why is the Bash shell script not running?
Also try to dos2unix the shell script, because sometimes it has Windows line endings and the shell does not recognize it. This helps sometimes. Unix has a variable called PATH that is a list of directories where to find commands.