4 ms·
I can foresee a new phenomenon arising in stackoverflow-style sites and coding discussion forums: "My simple piece of code looks perfect and should work withou
by pierrec 11y ago
I can foresee a new phenomenon arising in stackoverflow-style sites and coding discussion forums:
"My simple piece of code looks perfect and should work without problems. Yet it won't compile! Help!"
Answer:
"Try running `./mimic --reverse` on your source."
- po1nter 11y agoThat should be a comment.
- pierrec 11y agoTrue, except in the rare situation where the question really features a code sample containing some evil homographs. Edit: Oh hey, I actually found one that fits the bill: http://stackoverflow.com/questions/14925894/trouble-with-argc-and-argv http://stackoverflow.com/questions/14925894/trouble-with-arg...
- probably_wrong 11y agoI actually almost submitted something in that vein once. I'd type > ls | wc -l and get > bash: wc: command not found As it turns out, I need Alt+1 to type a pipe character in my keyboard. If I'm not quick enough releasing the Alt key, I'll type Alt+Space instead of just Space, which inserts a Non-breaking space[1] in Mac. This character is not a space, and therefore it gave me a weird "command not found" error. This lasted for months until I found out what the problem was - given that it was a combination of my keyboard settings and OS, finding the root of the error took quite some time. The hint? The "command not found" error had an extra space in front of the unknown command. [1] https://en.wikipedia.org/wiki/Non-breaking_space https://en.wikipedia.org/wiki/Non-breaking_space
- TazeTSchnitzel 11y agoThis bit me as well, as I mentioned in a comment above. The solution I found best was to make OS X not produce an NBSP on alt+space.