X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: Date: Wed, 30 Jul 2008 09:58:28 -0400 From: "Mark J. Reed" To: cygwin@cygwin.com Subject: Re: Can't use special characters \n or \r In-Reply-To: <001e01c8f24a$d3292590$9601a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <18725646.post@talk.nabble.com> <009601c8f226$8f3344c0$9601a8c0@CAM.ARTIMI.COM> <001e01c8f24a$d3292590$9601a8c0@CAM.ARTIMI.COM> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Wed, Jul 30, 2008 at 9:47 AM, Dave Korn wrote: > You omitted a vital qualifier from my earlier post ... Sorry. I certainly had no intention of misrepresenting what you said. I interpreted the newline thing not as a qualifier but as a separate point, which I didn't attempt to contradict. It's certainly true that you can't treat the newline like any other character with sed because of its line-oriented nature. But that doesn't change the fact that "normal" sed - at least, the one that comes in /usr/bin on Cygwin - does, in fact, "speak C-style escape chars". And since it has no trouble with carriage returns, the main thing the OP was trying to do works fine. Although, as y'all noted, d2u would be the simpler way to do it. -- Mark J. Reed -- 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/