Timeline for Script failing with "command not found: ^M"
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 6, 2012 at 12:06 | vote | accept | Amelio Vazquez-Reina | ||
| Sep 6, 2012 at 3:57 | comment | added | glenn jackman |
I think this error specifically comes from export LS_COLORS=$( \ -- the line continuation char must be the last character on the line and here it is followed by a carriage return.
|
|
| Sep 6, 2012 at 2:45 | history | edited | teppic | CC BY-SA 3.0 |
added 240 characters in body
|
| Sep 6, 2012 at 2:44 | comment | added | teppic | I'll update the main answer with the details. | |
| Sep 6, 2012 at 1:22 | comment | added | Amelio Vazquez-Reina |
Thanks @teppic! I see ... How should I run the script set_color_scheme.sh if I don't want to start a new shell? The problem I have is that the way I currently get on zsh is by invoking /bin/zsh from tcsh (the default shell in the system) as we are not "allowed" to change our default shell. My concern is that if source the file via . or source, it may invoke the default shell on it (tcsh), and not zsh. Is my concern unjustified? Should I just use source or . the file after calling /bin/zsh ?
|
|
| Sep 5, 2012 at 22:42 | history | answered | teppic | CC BY-SA 3.0 |