X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Kevin Markle Subject: Re: Newlines in cygwin help please... Date: Thu, 12 Apr 2007 15:04:09 -0400 Lines: 36 Message-ID: References: <01a001c77d30$83f19ba0$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <461E7F39 DOT 5090408 AT byu DOT net> Reply-To: kmarkle AT pbs DOT org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15"; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Eric Blake explained : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > According to Kevin Markle on 4/12/2007 12:40 PM: >> u2d $DIR/"$GROUP"_summary.rpt >> REPORT=`cat $DIR/"$GROUP"_summary.rpt` >> >> Get me this: > > How did it get you that? Are you echoing the contents of $REPORT, or > attaching the file $DIR/$GROUP_summary.rpt to your mail? I'm sending the value of $DIR/$GROUP_summary.rpt using febootimail which is a windows command line emailer. This is achieved by using cat to append to files. Each of which has had u2d run on it. > Are you using the cygwin-specific bash igncr control? I don't know what this is. > What mailer? Details are stilllacking... Mentioned above. > - -- > Don't work too hard, make some time for fun as well! Good thinking I tend to forget that... > Eric Blake ebb9 AT byu DOT net > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (Cygwin) > Comment: Public key at home.comcast.net/~ericblake/eblake.gpg > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFGHn8584KuGfSFAYARAhfEAKDFxPKbE4Iuxt1CNPYSzFSXgpAVhACePsJI > /oBzCd68lIjNDKeS4d7Z4ss= > =CS+A > -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/