Shell script execution error & #39; \ 357 \ 273 \ 277 & #39;: command not found solution, shell357

Shell script execution error '\ 357 \ 273 \ 277': command not found solution, shell357

1. Delete the BOM and execute the following command under vi.

:set nobomb

2. cause:

The so-called BOM is the Byte Order Mark, which is a Unicode character that usually appears at the beginning of the text to identify the Byte Order (Big/Little Endian ), in addition, you can also identify the encoding (UTF-8/16/32)

For UTF-8/16/32, 8/16/32 in their names refer to the number of bits in the encoding unit, that is, their encoding units are 8/16/32 bits, to convert to byte is 1/2/4 bytes, if it is multi-byte, it will involve the byte order, the UTF-8 in a single byte as the encoding unit, so there is no byte order. The main advantage of UTF-8 is that it can be compatible with ASCII, but if you use BOM, this advantage is gone, in addition, the existence of BOM may also lead to some problems. So we need to check and delete BOM in UTF-8 coding.

Reference: http://huoding.com/2011/05/14/78

Shell script prompts command not found

1. About command not found, this is because the PATH in 'path = 'ls $ RESULT | grep $ filename' overwrites the system environment variable. Change the PATH to a word such as Path or mypath.

2. make sure that all the variables are in the correct case. FAULS is used when you define them, and $ Fauls is used when you use the variables. As a result, the variable $ Fauls is empty, if [$ PATH = $ Fauls] is equivalent to if [$ PATH =].

3. when writing a statement such as if [$ PATH = $ Fauls], double quotation marks should be placed on the variable to prevent the syntax error "line 13 :[: too upload arguments ".

Shell script programming, prompt command not found

Paste all the code... you did not mention the information about the year and month of cal. · you suddenly said that cal was not found, I don't understand ····