Re: Spurious warning generated by bash
Andrey Repin via Cygwin <[email protected]>
| Newsgroups | gmane.os.cygwin |
|---|---|
| Message-ID | <[email protected]> |
Greetings, matthew patton! > since when is it acceptable to have UTF-8 format files as shell scripts, > perl scripts or even python programs? Since… forever? UTF-8 is compatible with ASCII on that level. The problem when you see `#!/xxx: No such file or directory` error is (either) a so-called "byte order mark" (which is not quite the same as UTF-16 BOM), or a CRLF line ending. > a directive in .vimrc can probably help. along the lines of > au BefRead,ButNewFile *.sh,*.pl,*.py set nobomb > or if you invoke your shell script with `bash --utf8 > ./my_broken^H^H^H^Hutf-encoded.script` or just `LANG=C.UTF-8 ./my_utf8-script` or set LC_ALL etc. > you know how people pose the question "if you could go back in time, would > you kill Hitler? Same needs to be asked about the person/committee that came up with UTF8. I suggest the https://www.joelonsoftware.com/articles/Unicode.html for an answer. -- With best regards, Andrey Repin Thursday, January 1, 2026 20:08:58 Sorry for my terrible english... -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple