X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <20090728091647.GK18621@calimero.vinschen.de> References: <4A6EBFE9.7080007@shaddybaddah.name> <20090728091647.GK18621@calimero.vinschen.de> Date: Thu, 30 Jul 2009 15:05:40 -0400 Message-ID: Subject: Re: [1.7] bash UNC path bug? From: "Mark J. Reed" To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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 Tue, Jul 28, 2009 at 5:16 AM, Corinna Vinschen wrote: > Works fine in tcsh. tcsh uses the csh style of nested backticks, where the inner backticks are doubled instead of backslashed. So the backticks don't introduce any extra level of backslash parsing. Also of note when testing this sort of thing is that tcsh's echo parses backslash escapes like bash's "echo -e" does: bash$ echo '\\' \\ tcsh$ echo '\\' \ -- Mark J. Reed -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple