How did I find this out? Because Bash is stupid and doesn't understand that a carriage return is a line delimiter. Instead it thinks the character is a literal character (like a letter or number), and so turns
mkdir /foo/bar. This creates a directory named "bar" followed by a carriage return. Which of course appears as merely "foo" in a web page, leading to all sorts of fun questions as to why a listing of
/fooclaims "bar" exists when listing
/foo/barreturns an error.
But surely we can get around this with quoting? Surely
mkdir "/foo/bar"will work?
Nope! See, Bash tries to be clever, and moves the
inside the quote marks. Seriously. It then runs
mkdir "/foo/bar. "
I eventually resorted to putting a comment at the end of every line to get this to work (and no, the obvious fix of using Linux line endings was not possible because this script was being entered in a web page, and line endings in web page forms are always normalised to
A bit of background for non-techies: computers these days generally use one of two sets of control characters to end a line of text. Windows uses a carriage-return/line-feed pair (
), while Linux uses just a line-feed (
). Most of the time this isn't an issue as any text editor smarter than Notepad understands either style.