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 Message-ID: <003801c278a6$98c05140$2c0f530c@mike> From: "mike parks" To: References: Subject: Re: Fw: problem with ls and similar commands in tcsh Date: Sun, 20 Oct 2002 21:07:23 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Igor, > On the tcsh command line, type 'ls temp*' (no Enter), then press Ctrl-X > and then press '*'. This should expand to the three filenames below. If > it instead expands to 'temp\*', you probably have noglob set > Another way of checking whether noglob is set is 'set | grep noglob' at > the tcsh prompt. 'ls temp* Ctrl-X *' gets expanded to temp/* i have not (yet) set up any .[c,t]shrc files yet. > If noglob is set, try 'unset'ting it and executing 'ls temp*' again. If > that makes it work, you have to track down which startup script sets > noglob (probably ~/.tcshrc, ~/.cshrc or /etc/csh.cshrc). Try starting > tcsh with the '-f' option to not execute those scripts, and see if it > fixes the problem. You will then want to edit the offending script and > comment out the 'set noglob' line. 'unset noglob' fixed the problem. many thanks Igor! mike -- 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/