StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>": Command not found" is the error I've seen when a UNIX/Linux shell script has been (mis-)handled by an MS Windows system. For example if it was checked out using a WebCVS, modified using Notepad or WordPad, and then re-submitted.</p> <p>(It's complaining that it can't find the [Ctrl-M] executable --- which is a perfectly valid, though extremely inconvenient and somewhat suspicious filename for UNIX/Linux).</p> <p>Run the file through GNU <code>cat -A</code> or the <code>od -x</code> or <code>hexdump</code> commands to see these (and verify my diagnosis ... or run it through <code>tr -d</code> with the appropriate quoting and shell "verbatim" handling for your system. (For example <code>tr -d '[Ctrl-V],[Ctrl-M]'</code> under Bash on a typical Linux system).</p> <p>Depending on your version of <code>tr</code> you might be able to use: <code>tr -d '\r'</code> or <code>tr -d \015</code> (015 is the octal for CR, "carriage return" or ^M --- MS-DOS used to used CR/LF pairs as line termination, which is just one of the many reasons that MS-DOS can rot in the forsaken abyss when it comes to interoperability. Line terminators of single characters cause no real issues for anyone else ... but PAIRS cause real conversion issues when everything else in the history of mainstream computing used single characters for this).</p> <p>Oh, yeah, <strong><em><code>vim</code></em></strong> has a handy <code>set ff</code> (a.k.a. <code>set fileformat</code> option which can handle UNIX, MacOS, and MS-DOS line termination conventions from any copy of <code>vim</code> regardless of which platform you're on. I seem to recall the <code>vim</code> default is to detect which types of line termination a file is using and leave it unchanged (and to default to your platform's native for any new files, of course).</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload