From: Pavel Rozenboim <pavelr@coresma.com>
To: cygwin <cygwin@cygwin.com>
Subject: RE: found problem in cygwin 1.3.14-1...
Date: Tue, 29 Oct 2002 02:38:00 -0000 [thread overview]
Message-ID: <7BCD42353C1FD411A66200062939B2F1ACA415@EXCHANGE> (raw)
You may need to fix your /etc/passwd file to fix permissions. Backup
/etc/passwd, and run mkpasswd -d -u <username> >> /etc/passwd.
> -----Original Message-----
> From: Randall R Schulz [mailto:rrschulz@cris.com]
> Sent: Tue, October 29, 2002 6:02 AM
> To: cygwin
> Subject: Re: found problem in cygwin 1.3.14-1...
> Importance: High
>
>
> 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@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/
>
--
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/
next reply other threads:[~2002-10-29 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 2:38 Pavel Rozenboim [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-28 20:40 Jason Fu
2002-10-28 22:52 ` Randall R Schulz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7BCD42353C1FD411A66200062939B2F1ACA415@EXCHANGE \
--to=pavelr@coresma.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).