From mboxrd@z Thu Jan 1 00:00:00 1970 Mime-Version: 1.0 (Apple Message framework v753) In-Reply-To: <53472026c675f17f73dc365162944a7d@comcast.net> References: <53472026c675f17f73dc365162944a7d@comcast.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Pietro Gagliardi Subject: Re: [9fans] Mac OS X Drawterm Oddity Date: Mon, 31 Dec 2007 12:57:31 -0500 To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Topicbox-Message-UUID: 248aba42-ead3-11e9-9d60-3106f5b1d025 That's not a newline, that's a carriage return. Two different things. OS X automatically converts the two formats - which are used by different computer operating systems - and some editors allow you to do it manually. Windows uses a carriage return followed by a newline. From nemo's guide, if you give a Plan 9 a Windows file, it would look like a(cr) b But if you give Windows a Plan 9 file, it would look like an a with a b on top. OS X doesn't care. On Dec 31, 2007, at 12:53 PM, Gregory Pavelcak wrote: > Now I'm confused. I was talking about snarfing the visible > (well OK, newlines are visible, but I mean the one with a > little 'C' at 11 o'clock and a little 'R' at 5 o'clock) > unicode character 000d, but the first email message > I sent out went out with the little CR character and came back to > me with newlines. Just the sort of thing I did not want to have > happen. It's simple, I just think that what I paste should look > just like what I just cut. How else should it look? > > Greg