From: Frank-Michael Moser <moser@decodon.com>
To: cygwin@cygwin.com
Subject: bash 2.05-3: completion
Date: Thu, 03 May 2001 02:27:00 -0000 [thread overview]
Message-ID: <3AF12453.36FB0032@decodon.com> (raw)
Hi,
it seems to me that tab completion for scripts is broken in
bash 2.05-3. Suppose a script updatedb in /usr/local/bin.
Typing "upd<TAB>" gives whether a completion nor alternatives.
Changing dir to /usr/local/bin and typing "./upd<TAB>" dito.
But copying /usr/local/bin/updatedb to /usr/local/bin/updatedb.exe
and typing "upd<TAB>" completes to updatedb.exe!?
This problem is not specific to updatedb or /usr/local/bin/.
I switched back to bash 2.05-3 and the problem is gone.
Frank-Michael
P.S. of course my scripts contain #!/bin/sh
or #!/bin/bash as first line.
begin:vcard
n:Moser;Frank-Michael
tel;work:+49-(0)3834-515230
x-mozilla-html:FALSE
url:www.decodon.com
org:DECODON GmbH
version:2.1
email;internet:moser@decodon.com
adr;quoted-printable:;;W.-Rathenau-Str. 49a=0D=0A;Greifswald;;17489;Germany
fn:Frank-Michael Moser
end:vcard
next reply other threads:[~2001-05-03 2:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-03 2:27 Frank-Michael Moser [this message]
2001-05-03 3:08 ` Frank-Michael Moser
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=3AF12453.36FB0032@decodon.com \
--to=moser@decodon.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).