Timeline for Why are special characters such as "carriage return" represented as "^M"?
Current License: CC BY-SA 3.0
29 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 1, 2014 at 9:22 | audit | First posts | |||
| Jul 1, 2014 at 9:39 | |||||
| Jun 26, 2014 at 7:17 | audit | First posts | |||
| Jun 26, 2014 at 7:17 | |||||
| Jun 21, 2014 at 12:18 | audit | First posts | |||
| Jun 21, 2014 at 12:19 | |||||
| Jun 12, 2014 at 9:14 | audit | First posts | |||
| Jun 12, 2014 at 9:14 | |||||
| Jun 11, 2014 at 8:23 | history | edited | Oliver Salzburg | CC BY-SA 3.0 |
There's no need to mark edits, we have a revision history
|
| Jun 9, 2014 at 19:36 | comment | added | Wayne Werner | I knew you could actually use ctrl+i as tab (I use it on connectbot on my phone in vim) I didn't realize that ^M works the same way, and they work basically everywhere. Cool! | |
| Jun 9, 2014 at 0:51 | answer | added | RonJohn | timeline score: 2 | |
| Jun 6, 2014 at 23:05 | comment | added | Daniel R Hicks | Has nothing to do with "letter of the alphabet", other than when the ASCII table was laid out the alpha characters were assigned sequentially, starting from 0x41. | |
| Jun 6, 2014 at 22:01 | answer | added | Daniel R Hicks | timeline score: 14 | |
| Jun 6, 2014 at 18:30 | comment | added | Daniel R Hicks | Because Control-M was the ASR-33 TTY keyboard combination to get the character. (And yes, Brian, Ctrl-G does ring a bell.) | |
| Jun 6, 2014 at 14:32 | answer | added | Don | timeline score: 3 | |
| Jun 6, 2014 at 7:43 | comment | added | Olivier Dulac | @JonHanna: apologies, i mixed in my comment carriage return and newlines. | |
| Jun 6, 2014 at 0:52 | history | tweeted | twitter.com/#!/super_user/status/474715412504911872 | ||
| Jun 5, 2014 at 21:47 | comment | added | Jon Hanna | @OlivierDulac ... U+000D is proleptic, since that name came with Unicode in the 1990s, but that does quite definitely reference the code as it existed in ASCII in 1963, anf through that as it existed in Murray's modified Baudot code in 1901. Murray was solving problems related to moving paper around, with the same tools used in the concept of "text file" many decades later. Hammer a screw into something like a nail, and it's still a screw. Use LF and/or CR to represent the end of a line in a text file, and they're still line-feeds and carriage returns. | |
| Jun 5, 2014 at 21:43 | comment | added | Jon Hanna | @OlivierDulac no, the ^M is exactly a carriage return, just like ^J is exactly a line-feed. While different OSs have had different views as to whether line-feed and/or carriage return or something else (like the Newline character used by some IBM characters but not part of ASCII and so not part of the historical heritage of some other OSs) should represent a new line in a text file, and while some programs have then overridden that in different ways, U+000D itself is still a carriage return, whatever later operating systems like Unix or DOS decided to do with it. (Of course, calling it... | |
| Jun 5, 2014 at 18:25 | answer | added | barlop | timeline score: 1 | |
| Jun 5, 2014 at 14:47 | comment | added | Olivier Dulac | the ^M you see when in linux (which uses "0x0a"(LF)) is probably from a file made on windows (which uses "0x0d 0x0a" (CR LF)). Thus, at the end of each line, you see the extra "0x0d" (CR). (the 0x0a being interpreted as a newline, and not shown in vi (well, it is : the next line will have a "~" if the previous line didn't end with a Newline). So the the ^M is not exactly a "carriage return", it's part of what a carriage return is in windows. The Answer tells why it's represented that way (using Caret Notation, ^@ = 0x00, ^A=0x01, etc..., ^M=0x0d, ...) | |
| S Jun 5, 2014 at 14:06 | history | edited | dotancohen | CC BY-SA 3.0 |
The intention of the question was clarified to be not about line terminators - so making title unambiguous, add tags
|
| S Jun 5, 2014 at 14:06 | history | suggested | Volker Siegel | CC BY-SA 3.0 |
The intention of the question was clarified to be not about line terminators - so making title unambiguous, add tags
|
| Jun 5, 2014 at 14:03 | review | Suggested edits | |||
| S Jun 5, 2014 at 14:06 | |||||
| Jun 5, 2014 at 13:28 | comment | added | user_1818839 | old one ... I can't remember the original code, but ctrl-G rings a bell! | |
| Jun 5, 2014 at 12:05 | comment | added | Jon Hanna |
@LatinSuD caret notation (and corresponding use of the Ctrl-key) relates to the C0 control set (historically part of ASCII) directly and not whether and how a given operating system or program uses part of that set in representing new lines, or anything else. Similarly, whether ^H deletes a character or allows overprinting (such as n^H~ as an obsolete way to produce ñ) or any other actual use of the control character is separate from the caret notation.
|
|
| Jun 5, 2014 at 9:17 | vote | accept | dotancohen | ||
| Jun 5, 2014 at 9:12 | answer | added | Art Gertner | timeline score: 121 | |
| Jun 5, 2014 at 9:02 | history | edited | dotancohen | CC BY-SA 3.0 |
added 19 characters in body
|
| Jun 5, 2014 at 8:47 | comment | added | LatinSuD | Also keep in mind that dos/windows use "0x0d 0x0a", also noted as "CR LF". But unix/linux use only "0x0a" or "LF". So when you open a windows document in linux it detects extra "CR", and when you open a linux document in windows it doesn't detect new lines. | |
| Jun 5, 2014 at 8:46 | answer | added | Ofir Luzon | timeline score: 0 | |
| Jun 5, 2014 at 8:38 | answer | added | Flup | timeline score: 23 | |
| Jun 5, 2014 at 8:31 | history | asked | dotancohen | CC BY-SA 3.0 |