'\r': command not found - .bashrc / .bash_profile [duplicate]

Answer 1

You can also add the option -o igncr to the bash call, e.g.

bash -x -o igncr script.sh

Answer 2

When all else fails in Cygwin...

Try running the dos2unix command on the file in question.

It might help when you see error messages like this:

-bash: '\r': command not found

Windows style newline characters can cause issues in Cygwin.

The dos2unix command modifies newline characters so they are Unix / Cygwin compatible.

CAUTION: the dos2unix command modifies files in place, so take precaution if necessary.

If you need to keep the original file, you should back it up first.

Note for Mac users: The dos2unix command does not exist on Mac OS X.

Check out this answer for a variety of solutions using different tools.

---

There is also a unix2dos command that does the reverse:

It modifies Unix newline characters so they're compatible with Windows tools.

If you open a file with Notepad and all the lines run together, try unix2dos filename.

Answer 3

Resolved with Notepad++ :

1) Menu->Edit->EOL Conversion -> Unix/OSX Format

2) Then Save

Fixed

Answer 4

SUBLIME TEXT

With sublime you just go to

View - > Line Endings -> (select)Unix

Then save the file. Will fix this issue.

Easy as that!

Answer 5

I had the same problem. Solution: I edit the file with pspad editor, and give it a unix format (Menu - Format -> UNIX)

I believe you can set this format to your file with many other editors

Answer 6

1. Choice

EditorConfig — is my choice.

---

2. Relevance

This answer is relevant for March 2018. In the future, the data from this answer may be obsolete.

Author of this answer personally used EditorConfig at March 2018.

---

3. Limitations

You need to use one of supported IDE/editors.

---

4. Argumentation

1. Simply usage. I need set my .editorconfig file 1 time, where I create my project, → I can forget some platform-, style- and IDE-specific problems.
2. Cross-platform, cross-languages, cross-IDE, cross-editors.

---

5. Example

5.1. Simple

I install EditorConfig plugin for Sublime Text → my text editor. I edit files in Sublime Text.

For example, I have sashacrlf.sh file:

echo "Sasha" &
echo "Goddess!" &

I run this file in Cygwin:

$ bash sashacrlf.sh
Sasha
sashacrlf.sh: line 1: $'\r': command not found
Goddess!

I create a file .editorconfig in same project as sashacrlf.sh.

[*.sh]
end_of_line = lf

It means, that if you save any file with .sh extension in your project in your editor, EditorConfig set UNIX line endings for this file.

I save sashacrlf.sh in my text editor again. I run sashacrlf.sh again:

$ bash sashacrlf.sh
Sasha
Goddess!

I can't get unexpected output in console.

5.2. Multiple file extensions

For example, I want to have UNIX line endings in all files with extensions .sh, .bashrc and .bash_profile. I add these lines to my .editorconfig file:

[*.{sh,bashrc,bash_profile}]
end_of_line = lf

Now, if I save any file with .sh, .bashrc or .bash_profile extension, EditorConfig automatically set UNIX line ending for this file.

---

6. Additional links

• EditorConfig official site.