Skip to main content
32 events
when toggle format what by license comment
Apr 25 at 6:58 answer added Toby Speight timeline score: 1
S Apr 25 at 6:49 history edited Toby Speight CC BY-SA 4.0
Make the title more specific
Apr 24 at 21:07 review Suggested edits
S Apr 25 at 6:49
Apr 24 at 15:29 answer added Alexander Ivanchenko timeline score: 2
Oct 1, 2014 at 5:14 answer added blitz timeline score: 1
Jan 16, 2014 at 14:21 vote accept asteri
Dec 18, 2013 at 0:25 history protected rolfl
Dec 17, 2013 at 2:54 comment added AJMansfield @WumpusQ.Wumbley Ideally, they really ought to work the same way STX and ETX ought to be used, to denote the start and end of textual data.
Dec 17, 2013 at 2:46 comment added AJMansfield @WumpusQ.Wumbley That is why we should stop referring to codepoints 0x0D and 0x0A as if they denoted line breaks. CR is really the line begin character, and LF is the line end character. CR's original purpose was to move the cursor to the beginning of the line and LF was to move the cursor off the current line.
Dec 14, 2013 at 18:38 comment added TC1 @JeffGohlke Most if not all DB export / import utils use a newline at the end. Winblows / M$SQL might as always be an exception, but it's common practice to have it there. I remember numerous times when I was almost ready to buy a plane ticket just to go over & slap the bastard who wrote stuff that didn't put it there.
Dec 14, 2013 at 17:18 history edited asteri CC BY-SA 3.0
added 377 characters in body
Dec 14, 2013 at 15:59 answer added scand1sk timeline score: 5
Dec 14, 2013 at 9:07 comment added user541686 @WumpusQ.Wumbley: I can't tell if you're being serious or sarcastic...
Dec 14, 2013 at 5:59 answer added theinsaneone timeline score: 2
Dec 14, 2013 at 4:55 answer added bobobobo timeline score: 2
Dec 13, 2013 at 23:41 comment added asteri @WumpusQ.Wumbley Interesting. But there's actually a specific reason I don't want a blank line at the end of the document. What I'm writing is a CSV file which will be uploaded line by line to a database. I'd rather have every line in the file legitimately be a row in the table, rather than having extraneous empty lines.
Dec 13, 2013 at 21:27 comment added supercat @WumpusQ.Wumbley: What term would you use to describe a file which encapsulates a sequence of lines, potentially followed by a partial line? The fact that concatenating such files will cause the partial line at the end of one to be joined to the first line of the second is often a bad thing, but is in some cases exactly what is required (especially when the second file contains only one line or partial line).
Dec 13, 2013 at 20:45 comment added GalacticCowboy @WumpusQ.Wumbley - One of the 16-bit Visual C++ compilers had a bug that would manifest when the source file did not end with CR/LF. But I haven't encountered anything else with such an issue in the past 15 years.
Dec 13, 2013 at 20:31 comment added zwol @DanielCook It's not just a Windows thing. Many Unix shell utilities, especially the older ones, behave unpredictably if the last line doesn't end in LF. On the other hand, sometimes the absence of a final LF is essential, as when using PHP to generate XML - if the PHP source file has a LF after the final ?>, it will be copied to the output and probably wind up in a place where the XML parser doesn't like it. So it's not by any means a hard rule.
Dec 13, 2013 at 20:17 comment added Daniel @WumpusQ.Wumbley It may be a windows thing, from wikipedia Text file : "MS-DOS and Windows use a common text file format, with each line of text separated by a two-character combination: CR and LF, which have ASCII codes 13 and 10. It is common for the last line of text not to be terminated with a CR-LF marker, and many text editors (including Notepad) do not automatically insert one on the last line."
Dec 13, 2013 at 20:15 comment added Daniel @WumpusQ.Wumbley In what circumstances would that ever be necessary? I'm not saying there are none, I just don't know of any. Arbitrarily declaring a format that all text files must follow seems overly ambitious.
Dec 13, 2013 at 19:36 comment added user33484 *Somebody has to say this... a text file is a series of lines. A line includes a newline terminator. A file that does not have a newline as its final character is not a text file. A file that ends in a blank line has 2 consecutive newlines as its last 2 characters: one to terminate the next-to-last line and one to terminate the empty line. "Text files" with an unterminated last line are a disease. Don't catch it!
Dec 13, 2013 at 19:33 history tweeted twitter.com/#!/StackCodeReview/status/411579575656009728
Dec 13, 2013 at 18:44 answer added ratchet freak timeline score: 5
Dec 13, 2013 at 18:36 answer added leonbloy timeline score: 5
Dec 13, 2013 at 18:34 answer added James Moughan timeline score: 6
Dec 13, 2013 at 17:02 answer added AJMansfield timeline score: 8
Dec 13, 2013 at 15:42 answer added smassey timeline score: 6
Dec 13, 2013 at 15:27 answer added rzymek timeline score: 13
Dec 13, 2013 at 15:16 history edited asteri CC BY-SA 3.0
added 32 characters in body
Dec 13, 2013 at 14:59 answer added rolfl timeline score: 24
Dec 13, 2013 at 14:38 history asked asteri CC BY-SA 3.0