File type: .py - Python. Probably happens on all file types, haven't had the need to test that premise.
Codepage: Automatic Detection (UTF 8 fallback) default.
Description: When saving .py file to a Linux samba share for execution on Linux (CentOS 6), the shebang line (#!/usr/bin/python) generates the following error on execution:
/usr/bin/python^M: bad interpreter
The ^M is the problem. The is a classic issue with Windows apps (like Code Writer) writing out the Windows EOL sequence instead of the Unix/Linux EOL sequence.
Requested Fix: Have EOL sequence selectable by file type in Win-C|Settings|File Type|<filetype>|Advanced. Certainly default it to Windows, but let us be able to choose.
Workaround: Not a Good One - run dos2unix <filename> on the linux box after every edit and before execution. Nasty, but it works. It also clearly identifies the problem.
[Modified 7 years ago]