Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Subject: RE: New output from mount.exe MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Mon, 2 Apr 2001 15:28:14 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 content-class: urn:content-classes:message Message-ID: Thread-Topic: New output from mount.exe Thread-Index: AcC7Mh1/yvs7Zf18SOGYX/eEEuFtcQAA4Ebg From: "Robert Collins" To: "DJ Delorie" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id BAA05681 > -----Original Message----- > From: DJ Delorie [mailto:dj AT delorie DOT com] > Sent: Monday, April 02, 2001 3:09 PM > To: Robert Collins > Cc: cygwin-developers AT cygwin DOT com > Subject: Re: New output from mount.exe > > > > > Sounds good. I do have a suggestion, not an objection - > > perhaps escaping the \\ & \ ? > > I think if we add the "mount --output-batch-file" option, *that* > should worry about backquotes. For just printing, it shouldn't be a > problem, and you really do want the backslashes for UNCs. > I was meaning like \\\\ for \\, so that bash et al won't get confused. (as opposed to skipping the \\'s). Rob