Oops! Re: [ale] Mac/Unix linefeed

[Eric Z. Ayers]

Of course, Marc is right.  Don't put CTRL-L characters in your files!

-Eric.

Marc Torres wrote:
> 
>         Eric, my good friend-- you got a typo in here!  Just thought
>         I'd drop you a reminder so you can clear it up on the list.
> 
>         UNIX uses CTRL-J = linefeed.
>         DOS uses CTRL-M + CTRL-J
>         CRTL-L is clear screen on most terminals or page eject on lpr's.
> 
>         Anyway hope this note finds you and your family well.
> 
>         Happy new year,
>         --marct
>         marct at mindspring.com
> 
> On Fri, 19 Jan 2001, Eric Z. Ayers wrote:
> 
> > If these are ASCII files, they need to put and retrieve them in ASCII
> > mode.  That's what ASCII mode is for.  It translates newlines to be
> > whatever is on the operating system you are using.  The files on the
> > UNIX host should have a CTRL-L at the end of each line.  After being
> > transferred to a DOS host, they will have CTRL-M, CTRL-L at the end of
> > each line.
> >
> > Jennifer Taylor wrote:
> > >
> > > Sorry for the length of this post, but this is driving me crazy and I can't find anything on the web about it other than what I already know...
> > >
> > > A client uses fetch to ftp files back and forth between a redhat 6.2 web server and a Mac running some unspecified os...something not osX.
> > >
> > > A month or so ago, we tar'd up all their files and moved them from an old, ugly rh5.2 box to a shiny new rh6.2 box.  That is the ONLY change that we made.  As far as we can ascertain, they have not made any changes to their fetch-ftp setup, but we don't do their tech support so who knows for sure.
> > >
> > > Well they were complaining that their files were coming in with no line breaks, but it looked fine on the server so obviously the \n's were in place, but not whatever macs need.  So we did unix2dos because all their text processors recognize the ^M as a line break.  And they were happy, and we managed to convince them to fetch put as raw data instead of text, because it was stripping out all the ^Ms and they were back at no line feeds.  So NOW, when I vi the file, lo and behold there's no \n's, only ^Ms, and so no line breaks for me...which is not optimal.
> > >
> > > This is a mess, and we can't figure out why moving from one server to another would cause something like this.  I don't see how it could've.  I maintain that it's the mac's fault.  Anyone got any ideas??   All help will be very much appreciated!
> > >
> > > jenn
> > > --
> > > To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.
> > --
> > To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.
> >
--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.