Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 From: "Robert Mark Bram" To: Subject: RE: cygpath question Date: Fri, 24 Jan 2003 20:20:55 +1100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal Importance: Normal In-Reply-To: <5.2.0.9.2.20030123224821.02dfc4a0@pop3.cris.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Howdy Randall, > > $ cdd C:\Rob\mcd3060\Tri32002\a2 > > bash: cd: C:Robmcd3060Tri32002a2: No such file or directory > In this case, the unquoted backslashes > essentially just disappear, since in > each case the character they precede > is not special. Thank you very much for your reply. I forgot the cardinal rule that arguments entered on the command line must be quoted if they include characters such as \ that are not meant as escape characters... All of this brings me to the rather depressing conclusion that I cannot make the same shortcut in cygwin that I often use in cmd.exe: copying a path from Windows Explorer, alt-tabbing to the command prompt, typing "cd " with the left hand then right clicking with the right hand and pressing enter to move easily to a new directory. Usually, this technique is still easier than the auto-complete functions available in bash and XP's cmd.exe... Rob :) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/