Now they just need to stop inserting UTF-8 BOMs into files and a whole entire class of newbie errors (and corresponding gatekeep-y responses) will be eliminated. Just imagine that.
-
-
-
Uhg. Does it do this when re-saving opened UTF-8 files, or only saving new files?
-
Unfortunately, I don't know. I do know that it's the classic cause of the PHP "headers already sent" error, and that the classic "fix" was to "just copy all of the contents into a new file and it works now." (At least SO now has a comprehensive explanation of this specific error)
End of conversation
New conversation -
-
-
Next on the backlog: vi quits properly
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.