I installed CygWin on Windows 7. Using Notepad, I edited my ~/.bash_profile file to add on to the PATH variable …


Now, when I SSH in to my Windows machine, I get this error …

-bash: $'\r': command not found
-bash: $'\r': command not found
-bash: $'\r': command not found
-bash: $'\r': command not found
-bash: $'\r': command not found
-bash: /home/dev/.bash_profile: line 39: syntax error: unexpected end of file

and my PATH is not set. Anyone know how I can correct this?

  • 1
    Egads, don't ever use notepad to edit a unix file. It adds the \r character at line endings, and as bash reported, it isn't tolerated very well. Run d2u .bash_profile to fix it. Also, you should ask questions like this on superuser not stackoverflow.
    – Amardeep
    Sep 1, 2011 at 13:40

3 Answers 3


As mentioned already, Windows uses \n\r as line separator. Now that you've got the \rs in your .bash_profile, however, you can use the utility dos2unix to remove them.

  • 3
    Windows uses \r\n, not \n\r. Sep 1, 2011 at 14:41

Probably notepad has added some $'\r', i. e. CR characters - as it is usual under Windows to have CRLF as line terminator.

The solution would be to use another editor which is capable to keep the line endings as they are, e. g. vim for Windows, or Notepad2.

  • This is not an answer. This is a comment.
    – musiKk
    Sep 1, 2011 at 13:54
  • 1
    I'm usually bothered by answers that should be comments, but this does imply that the OP should just stop using Notepad, and as such I think it qualifies as an answer (if not a very good one).
    – Pops
    Sep 1, 2011 at 20:04
  • Extended the answer in order to qualify as one. Are there any alternatives to changing the editor?
    – glglgl
    Sep 2, 2011 at 7:46

Depending on the environment you are using, you might be stuck with scripts containing CRLF, i.e. when using Visual SourceSafe, Perforce for Windows etc. to store your files. However, bash has a universal way to get around this problem:

set -o igncr

If you put this at the start of your .bash_profile or other startup script you may be using, you are out of trouble, as the CRLF sequences before the first command in your startup script do not hurt.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.