Mail Archives: cygwin/2002/10/30/10:36:21
Jason,
What permissions to "setup.log" and "setup.log.full" have on your system?
On my system it's like this:
-rwxrwxrwx 2 Administ None 171008 Jul 4 07:15 setup-2.249.2.5.exe*
-rwxrwxr-x 1 RSchulz None 206336 Jul 8 04:00 setup-2.259.2.4.exe*
-rwxrwxrwx 2 Administ None 171008 Jul 4 07:15 setup.exe*
-rwxrwxrwx 1 Administ None 510529 Oct 28 17:43 setup.log*
-rwxrwxrwx 1 Administ None 117007 Oct 28 17:43 setup.log.full*
% setup.log<TAB><TAB>
setup.log setup.log.full
% setup<TAB><TAB>
setup-2.249.2.5.exe setup.bmp setup.log setupdll.dll
setup-2.259.2.4.exe setup.exe setup.log.full
% chmod -x setup.log*
% setup.log<TAB><TAB>
<BEEP>
So you see, the behavior is predictable, controllable and correct.
Randall Schulz
Mountain View, CA USA
At 02:35 2002-10-30, you wrote:
>I don't think so. I think it's bug as shown below:
>
>===========================================================
>
>
>root AT KIRIN ~
>$ cd Shared\ Documents//ftp/cygwin/
>
>root AT KIRIN ~/Shared Documents/ftp/cygwin
>$ ls
>cygipc-1.11-1.tar
>ftp%3a%2f%2fmirrors.rcn.net%2fmirrors%2fsources.redhat.com%2fcygwin
>setup.exe
>setup.log
>setup.log.full
>
>root AT KIRIN ~/Shared Documents/ftp/cygwin
>$ ./setup.log
>./setup.log ./setup.log.full
>
>root AT KIRIN ~/Shared Documents/ftp/cygwin
>$ ./setup.log
>
>===========================================================
>
>I don't think setup.log and setup.log.full should be with execute permission
>but not setup.exe as shown above. It's a bug!
>
>
>Jason Fu
>
>
>Jason,
>
>In the command position command completion only includes files with execute
>permission.
>
>Since Cygwin 1.3.13, "ntsec" is on by default, when in the past it was off by
>default. No doubt your files don't have explicit execute permissions.
>
>You'll need to add explicit execute permissions to ".exe" files and
>scripts to
>get them to be expanded by filename completion in the way you want.
>
>I make a very quick scan of the READLINE section of the BASH manual and
>didn't
>see a way around this, but the sub-section "Programmable Completion" might
>hold an option / answer I didn't notice.
>
>Randall Schulz
>Mountain View, CA USA
>
>
>At 19:26 2002-10-28, you wrote:
>
>No more tab in bash shell available.
>
>I can't use tab to search programs like shutdown.exe by simply type the 'tab"
>key after typing "shu" as before:
>
>============================================
>
>$ ls /bin/sh{TAB]
>sh.exe shar.exe shred.exe
>sha1sum.exe showfigfonts shutdown.exe
>
>tsfu AT KIRIN ~/Shared Documents/pub
>$ shu[TAB]
>
>==================================
>
>No response at all.
>
>I could do so with 1.3.12 or before. In short, the "tab" function of bash no
>longer works properly as before.
>
>
>Regards,
>
>Jason Fu
--
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/
- Raw text -