9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Mac OS X Drawterm Oddity
Date: Mon, 31 Dec 2007 12:57:31 -0500	[thread overview]
Message-ID: <F4D6555D-6088-49D7-8F67-3F3880971248@mac.com> (raw)
In-Reply-To: <53472026c675f17f73dc365162944a7d@comcast.net>

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


  reply	other threads:[~2007-12-31 17:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-28 19:29 Gregory Pavelcak
2007-12-28 19:45 ` Gregory Pavelcak
2007-12-28 21:20   ` andrey mirtchovski
2007-12-28 21:45     ` Gregory Pavelcak
2007-12-31 12:30   ` Russ Cox
2007-12-31 17:53     ` Gregory Pavelcak
2007-12-31 17:57       ` Pietro Gagliardi [this message]
2007-12-31 18:09         ` Gregory Pavelcak
2007-12-31 19:08     ` Gary Wright

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F4D6555D-6088-49D7-8F67-3F3880971248@mac.com \
    --to=pietro10@mac.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).