On Mon 05 Sep 2005 at 14:05:22 +0200, you wrote: > X-Loop: [EMAIL PROTECTED] > Reply-To: [EMAIL PROTECTED], [EMAIL PROTECTED] > X-Debian-PR-Message: report 306043 > X-Debian-PR-Package: bash > X-Debian-PR-Keywords: > X-Mailer: reportbug 2.99.6 > Delivered-To: [EMAIL PROTECTED] > X-Virus-Scanned: by amavisd-new at cs.tu-berlin.de (including spamassassin) > X-Spam-Status: No, hits=0 tagged_above=0 required=3 tests= > X-Spam-Level: > Resent-From: Frederik Eaton <[EMAIL PROTECTED]> > Resent-To: debian-bugs-dist@lists.debian.org > Resent-Cc: Matthias Klose <[EMAIL PROTECTED]> > Resent-Date: Sat, 23 Apr 2005 22:33:02 UTC > Resent-Message-ID: <[EMAIL PROTECTED]> > Resent-Sender: Debian BTS <[EMAIL PROTECTED]> > From: Frederik Eaton <[EMAIL PROTECTED]> > To: Debian Bug Tracking System <[EMAIL PROTECTED]> > Subject: Bug#306043: bash executable completion doesn't work if there is a > space in the executable path > Date: Sat, 23 Apr 2005 15:20:19 -0700 > > Package: bash > Version: 3.0-8 > Severity: normal > > Bash executable completion doesn't work if there is a space in the > executable path. Causes problems especially on Mac OS X with its > quirky pathnames.
To be clear, are you talking about command completion (i.e. completion of the first token on the command line) or completion of a subsequent token? The former case is handled by bash itself, the latter by the bash completion shell code. Ian -- Ian Macdonald | Where is John Carson now that we need him? [EMAIL PROTECTED] | -- RLG http://www.caliban.org/ | | | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
