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: Sat, 19 Oct 2002 20:39:32 -0400 From: Jon LaBadie To: cygwin AT cygwin DOT com Subject: Re: Fw: problem with ls and similar commands in tcsh Message-ID: <20021020003932.GA8613@butch.jgcomp.com> References: <005101c277b5$25b94540$4810530c AT mike> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <005101c277b5$25b94540$4810530c@mike> User-Agent: Mutt/1.3.28i On Sat, Oct 19, 2002 at 04:19:01PM -0500, mike parks wrote: > igor, > > ----- Original Message ----- > From: "Igor Pechtchanski" > To: "mike parks" > Cc: > Sent: Saturday, October 19, 2002 3:30 PM > Subject: Re: Fw: problem with ls and similar commands in tcsh > > > > > *** 2) is there anything else i need to do as well to solve this > problem? > > > > Hard to say. Are the files you're looking for actually there? Does 'dir > > temp*' do what you want? How about 'cmd /c "dir temp*"'? > > the files are there. the ls/dir commands work fine in the default bash > shell. i get the > problem when i try to run in a tcsh. silly question, have you done a set noglob? -- Jon H. LaBadie jcyg AT jgcomp DOT com JG Computing 4455 Province Line Road (609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) -- 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/