From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luciano Miguel Ferreira Rocha Subject: Re: ctrl-M Date: Wed, 27 Aug 2003 20:34:31 +0100 Sender: linux-admin-owner@vger.kernel.org Message-ID: <20030827193431.GA7584@lsd.di.uminho.pt> References: <3F4D0079.9060106@ashlee.info> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <3F4D0079.9060106@ashlee.info> List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Shawn Ashlee Cc: linux-admin@vger.kernel.org On Wed, Aug 27, 2003 at 12:03:21PM -0700, Shawn Ashlee wrote: > I have a bash script writting to a .procmailrc file, but it is putting > in ctrl-M's where I have \r or \015. You can see them in vi but not when > you cat the file. It wouldn't be a problem, but procmail cant read it > with those in there. I tried \n, but it adds alot of blank lines. > The archives mostly talk about compatability for dos/linux, but that > doesnt help me. There are a lot of options for converting files between 'dos' style (\r\n as line separators) and the 'unix' style (only \n is used): * dos2unix or unix2dos * tr -d '\r' < dos_file > unix_file * vi: edit file and set the fileformat option to unix or dos and save: vi zbr :set fileformat=unix ZZ Regards, Luciano Rocha