This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: spaces in .bash_profile lead to "command not found"


Peter Jay Salzman wrote:
There are 4 blank lines in my .bash_profile:
[snip]

Each blank line generates an error:

   $ source .bash_profile
   BEGIN ~/.bash_profile
   : command not found
   : command not found
   : command not found
   : command not found
   END ~/.bash_profile

However, if I comment all the blank lines out, I get no errors.  Each blank
line in this file seems to be causing a "command not found" error.  What
could be causing this?

Have you eliminated CR's as the cause (RTFRA and STFLA if you don't know what I'm talking about). What version of bash are you using? It would be helpful if you read http://cygwin.com/problems.html, especially the part about ATTACHING (not pasting in-line) cygcheck output.


(Ooh... google finds lots of "wrong" results for STFLA, but the second RTFRA is my big-nasty-rant one ;-).)

--
Matthew
Don't use a hippo to... what was I saying?


-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]