X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=BAYES_00,TW_YG X-Spam-Check-By: sourceware.org From: Gary To: cygwin AT cygwin DOT com Subject: Re: cygpath behaviour when input is not a path References: <83d3wff7t5 DOT fsf AT garydjones DOT name> Mail-Followup-To: cygwin AT cygwin DOT com Date: Sat, 29 May 2010 17:20:55 +0200 In-Reply-To: <83d3wff7t5.fsf@garydjones.name> (Gary's message of "Sat, 29 May 2010 10:09:26 +0200") Message-ID: <837hmmenu0.fsf@garydjones.name> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (cygwin) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 I wrote: > How should cygcheck cygpath, not cygcheck /me smacks head > behave when given a "PATH list" (e.g., > '/bin:/usr/bin'), *without* the -p option? > > For example: > $ cygpath -a -p -C ANSI -w /bin:/usr/bin > C:\cygwin\bin;C:\cygwin\bin > > = okay. What I expect from RTFMP. > > $ cygpath -a -C ANSI -w /bin:/usr/bin > C:\cygwin\bin?\usr\bin > > Urk! I would have hoped it wouldn't try to convert this, or at the very > least not the last part, but I don't know if it's a bug, "by design", or > what. > > Basically what I am trying to work out is how trustworthy cygpath is > when it receives input that isn't actually a path (for example when it > receives output from a program, some of which might be paths and some of > which might not be). -- Gary Non-kook (allegedly) -- 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