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: <3E5D738B.3030906@netstd.com> Date: Thu, 27 Feb 2003 10:10:19 +0800 From: Wu Yongwei Organization: Kingnet Security, Inc. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en, en-us, zh-cn, zh MIME-Version: 1.0 To: cygwin Subject: cygwin1.dll, nontsec, and NTFS disk issue Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit With newer versions of cygwin1.dll (maybe 1.3.15 and later), the ntsec/nontsec behaviour has changed. Now ntsec is the default, and even when nontsec is specified, the command-line autocomplete still behaves like ntsec when operating on a NTFS disk, i.e., when I have a test.c and a test.exe, ". / t e s t TAB" will bring only "./test." instead of the expected "./test.exe". I don't think it affects many people, but it really frets me. I stayed with cygwin 1.3.12-4 for a long while, but now I see more and more packages depend on new features of newer versions of cygwin.... Thanks for any possible help/suggestions. Best regards, Wu Yongwei -- 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/