From owner-freebsd-questions Mon Nov 5 20:45: 4 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail5.nc.rr.com (fe5.southeast.rr.com [24.93.67.52]) by hub.freebsd.org (Postfix) with ESMTP id 7FF0137B418 for ; Mon, 5 Nov 2001 20:44:47 -0800 (PST) Received: from i8k.babbleon.org ([66.57.85.154]) by mail5.nc.rr.com with Microsoft SMTPSVC(5.5.1877.687.68); Mon, 5 Nov 2001 23:44:40 -0500 Content-Type: text/plain; charset="iso-8859-1" From: Brian T.Schellenberger To: "David Loszewski" , Subject: Re: ^M on end of lines Date: Mon, 5 Nov 2001 23:44:31 -0500 X-Mailer: KMail [version 1.2] References: <000301c1667a$63e4b220$3000a8c0@sickness> In-Reply-To: <000301c1667a$63e4b220$3000a8c0@sickness> MIME-Version: 1.0 Message-Id: <01110523443105.00915@i8k.babbleon.org> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Monday 05 November 2001 23:20, David Loszewski wrote: > K, I'm getting what you're saying, but if they're normal to have in a > file, why would they effect the way that a file such as a .cgi or .pl > file runs? Well, they mess up the #! line at the start, but otherwise perl ignores them, in my experience.:w But the *aren't* normally present in "ordinary" edited files, like perl scripts; they *are* normally present in typescript files; and one normally *does* strip them when getting files from MS-DOS; if you FTP them in text mode, then this will normally be done for you; otherwise numerous tools can strip them for you. But this is all normal, run-of-the-mill Unix behavior. > > > Dave > > -----Original Message----- > From: Brian T. Schellenberger [mailto:bts@babbleon.org] > Sent: Monday, November 05, 2001 12:10 AM > To: David Loszewski > Cc: freebsd-questions@FreeBSD.ORG > Subject: Re: ^M on end of lines > > On Sunday 04 November 2001 23:52, you wrote: > > Thx for your help, and I'm just using the regular vi that comes with > > FreeBSD 4.4 > > Did I imagine it or did you say that you had experienced differnet > behavior > in some other environment? > > Or, to put it another way, what's the *problem* with ^Ms that you are > trying > to solve? > > The mere presence of Carriage-returns in a file would not normally be > thought > of as a problem. > > > Dave > > > > -----Original Message----- > > From: Brian T. Schellenberger [mailto:bts@babbleon.org] > > Sent: Sunday, November 04, 2001 10:17 PM > > To: David Loszewski; freebsd-questions@FreeBSD.ORG > > Subject: Re: ^M on end of lines > > > > On Saturday 03 November 2001 23:29, David Loszewski wrote: > > > So then how do I strip it of the '^M's then? Lol, this is the > > biggest > > > > pain in the ass, and I'm not a complete newbie. > > > > I'm still trying to get what's different or surprising about > > this--nothing > > should be any different w/r/t FreeBSD & ^M vs. any other Unix-like > > O/S. > > > If something *is* different, you must be using a different editor or > > capture > > process or *something* than what you used before. > > > > > If I do 'wget' I get the > > > same thing sometimes so I'm starting to think that there's something > > > wrong with the configs in the system. Ideas on where I should start > > > looking? > > > > I've attached the scripts that I actually use to do this. Just put > > both > > > of > > them in a directory that's in your path & you're all set. I've tossed > > "all" > > in for good measure; you can use > > > > unmsdos *.* > > > > to make all of the files "Unixy" or > > > > all '*.*' 'uncrnl $i' > > > > to just un-cr-nl them. > > > > I'm sure that there are standard utilities to do this, but this is > > literaly > > what I do. > > > > > Dave > > > > > > -----Original Message----- > > > From: Ryan Thompson [mailto:ryan@sasknow.com] > > > Sent: Saturday, November 03, 2001 12:54 PM > > > To: Brian T.Schellenberger > > > Cc: David Loszewski; freebsd-questions@FreeBSD.ORG > > > Subject: Re: ^M on end of lines > > > > > > Brian T.Schellenberger wrote to David Loszewski: > > > > On Friday 02 November 2001 19:59, you wrote: > > > > > Maybe the question I should be asking instead is, is it normal > > to > > > > see a > > > > > > > > crap load of '^M's in a file in FreeBSD? > > > > > > > > Never happens to me (except with MS-DOS files, and of course that > > > > > > happens in > > > > > > > Linux as well). So something is configured in a screwy way on our > > > > > > system if > > > > > > > it's any different from Linux. > > > > > > > > But here's the deal on FTP, as I understand it: > > > > > > > > in text mode, FTP uses the MS-DOS conventions (it adds ^Ms), so if > > > > you > > > > > > run FTP on Linux in text (ascii) mode but the FTP on FreeBSD in > > > > binary > > > > > > mode, then Linux will add the ^Ms and FreeBSD won't strip 'em. > > > > > > Not the case.. Unless maybe your FTP is broken? > > > > > > > If you are running *nix-to-*nix, then FTP in binary mode on both > > > > ends; > > > > > > if it's a text file you can use text mode on both ends. Sounds > > like > > > > > somehow the FTPs aren't communicating and they are in different > > > > modes. > > > > > > Of course that's not supposed to be possible, and I've never seen > > > > it, > > > > > > but it sounds like what might be happenening to you anyway. > > > > > > Actually, what ASCII mode is supposed to do, is, when transferring > > > > text > > > > > files, convert to the platform specific text format. (Which really > > > > means > > > > > the receiver strips or adds the ^M). This instruction is actually in > > > > our > > > > > training manual for new employees developing code on Windows > > machines > > > > who > > > need to transfer via FTP. USE ASCII MODE FOR ASCII FILES. :-) > > > > > > - Ryan > > > > > > > > Dave > > > > > > > > > > > > > > > -----Original Message----- > > > > > From: owner-freebsd-questions@FreeBSD.ORG > > > > > [mailto:owner-freebsd-questions@FreeBSD.ORG] On Behalf Of > > undergra > > > > > > Sent: Friday, November 02, 2001 7:28 PM > > > > > To: Andreas Ntaflos; David Loszewski > > > > > Cc: freebsd-questions@FreeBSD.ORG > > > > > Subject: RE: ^M on end of lines > > > > > > > > > > tr -d "\015" < input-file > output-file > > > > > ----- Mensaje original ----- > > > > > De: "Andreas Ntaflos" > > > > > Para: "David Loszewski" > > > > > CC: > > > > > Enviado: sábado, 03 de noviembre de 2001 0:44 > > > > > Asunto: Re: ^M on end of lines > > > > > > > > > > > On Fri, Nov 02, 2001 at 05:43:18PM -0500, David Loszewski > > wrote: > > > > > > > Yea, but then I have to do that to all the files > > > > > > > Not pretty when you have a 100 files > > > > > > > > > > > > > > Dave > > > > > > > > > > > > > >> a simple fix after dl is to open it up in vi and do > > > > > > >> > > > > > > >> :%s,^V^M,,g > > > > > > >> > > > > > > >> -r > > > > > > > > > > > > The following perl command issued on the CLI will get > > > > > > rid of these annoying ^Ms. > > > > > > > > > > > > # perl -e -i -p 's/\r\n/\n/s' filename > > > > > > > > > > > > you can use wildcards too. > > > > > > > > > > > > There are also ports to solve these problems, like dos2unix. > > > > > > > > > > > > regards > > > > > > -- > > > > > > Andreas "ant" Ntaflos > > > > > > ntaflos.andreas@gmx.net > > > > > > Vienna, AUSTRIA > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > > with "unsubscribe freebsd-questions" in the body of the > > message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > with "unsubscribe freebsd-questions" in the body of the message -- Brian T. Schellenberger . . . . . . . bts@wnt.sas.com (work) Brian, the man from Babble-On . . . . bts@babbleon.org (personal) http://www.babbleon.org -------> Free Dmitry Sklyarov! (let him go home) <----------- http://www.eff.org http://www.programming-freedom.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message