From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12282 invoked by alias); 24 Nov 2001 03:10:13 -0000 Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Received: (qmail 12261 invoked from network); 24 Nov 2001 03:10:12 -0000 Received: from unknown (HELO femail20.sdc1.sfba.home.com) (24.0.95.129) by sourceware.cygnus.com with SMTP; 24 Nov 2001 03:10:12 -0000 Received: from althea.tishler.net ([24.3.200.94]) by femail20.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP id <20011124031012.FMVF6645.femail20.sdc1.sfba.home.com@althea.tishler.net>; Fri, 23 Nov 2001 19:10:12 -0800 Received: by althea.tishler.net (sSMTP sendmail emulation); Fri, 23 Nov 2001 22:13:28 -0500 Date: Thu, 15 Nov 2001 12:26:00 -0000 From: Jason Tishler To: Thomas Harte Cc: Cygwin Subject: Re: Whither a2ps.exe? Message-ID: <20011123221328.D500@dothill.com> Mail-Followup-To: Thomas Harte , Cygwin Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <231101327.60974@webbox.com> User-Agent: Mutt/1.3.18i X-SW-Source: 2001-11/txt/msg00927.txt.bz2 Thomas, In the future, please post to cygwin@cygwin.com instead of sending private email so others can benefit too. On Fri, Nov 23, 2001 at 04:56:15PM -0800, Thomas Harte wrote: > I'm getting problems when I execute a2ps, however: > > $ a2ps --file-align=fill --medium=Letter --toc ./*.m -o prt2.ps > a2ps:/usr/local/etc/a2ps.cfg:7: invalid option `\r' > > so I followed a tip I found in another post to replace blank > lines in the /usr/local/etc/a2ps*.cfg files with '#' but that > generated the following: > > $ a2ps --file-align=fill --medium=Letter --toc ./*.m -o prt2.ps > a2ps:/usr/local/etc/a2ps.cfg:150: invalid option `#?o!cat!psnup' > > and so on. > > Have you come across the above problems? No. > Any suggestions? The above sounds like a text vs. binary mode problem. Does a2ps.cfg have CRNL line endings? If so, then convert it and the other configuration files to binary mode (i.e., NL line endings). Otherwise, complete the port so that a2ps can tolerate text mode configuration files. Please search the mailing list archives for the various way to accomplish this. Thanks, Jason -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Tishler To: Thomas Harte Cc: Cygwin Subject: Re: Whither a2ps.exe? Date: Fri, 23 Nov 2001 19:10:00 -0000 Message-ID: <20011123221328.D500@dothill.com> References: <231101327.60974@webbox.com> X-SW-Source: 2001-11/msg01515.html Message-ID: <20011123191000.-vp7X6MgLzFdC5rN9l1RwS4-juJNYyGCvQMuD1B7aEU@z> Thomas, In the future, please post to cygwin@cygwin.com instead of sending private email so others can benefit too. On Fri, Nov 23, 2001 at 04:56:15PM -0800, Thomas Harte wrote: > I'm getting problems when I execute a2ps, however: > > $ a2ps --file-align=fill --medium=Letter --toc ./*.m -o prt2.ps > a2ps:/usr/local/etc/a2ps.cfg:7: invalid option `\r' > > so I followed a tip I found in another post to replace blank > lines in the /usr/local/etc/a2ps*.cfg files with '#' but that > generated the following: > > $ a2ps --file-align=fill --medium=Letter --toc ./*.m -o prt2.ps > a2ps:/usr/local/etc/a2ps.cfg:150: invalid option `#?o!cat!psnup' > > and so on. > > Have you come across the above problems? No. > Any suggestions? The above sounds like a text vs. binary mode problem. Does a2ps.cfg have CRNL line endings? If so, then convert it and the other configuration files to binary mode (i.e., NL line endings). Otherwise, complete the port so that a2ps can tolerate text mode configuration files. Please search the mailing list archives for the various way to accomplish this. Thanks, Jason -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/