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 Date: Mon, 13 May 2002 13:39:22 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: cygwin tcsh-related regression bug Message-ID: <20020513133922.E6264@cygbert.vinschen.de> Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.22.1i On Thu, May 09, 2002 at 07:34:56PM -0700, C. J. wrote: > > Cygwin 1.3.10 seems to generate a problem with filename completion in tcsh > that did not exist on cygwin 1.3.5-3. If I have a file 'File.cpp' in a > directory, typing 'cp F[TAB]' at the prompt (where [TAB] represents the TAB > key) causes completion to 'cp File.cpp', but if I type 'cp X.cpp F[TAB]', > the 'F' is not completed to 'File.cpp', instead nothing happens. It seems Try the same with `echo' instead of `cp'. If that works (it's working for me) it's one of the funny completion restrictions to pamper the user. Hint: cp a b would delete b if it exists... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/