On Mon 05 Sep 2005 at 14:16:11 +0200, you wrote: > X-Loop: [EMAIL PROTECTED] > Reply-To: Justin Pryzby <[EMAIL PROTECTED]>, [EMAIL PROTECTED] > Original-Sender: Justin Pryzby <[EMAIL PROTECTED]> > X-Debian-PR-Message: report 297065 > X-Debian-PR-Package: bash > X-Debian-PR-Keywords: > X-Mailer: reportbug 3.8 > X-Virus-Scanned: by amavisd-new at stlawu.edu > 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: Justin Pryzby <[EMAIL PROTECTED]> > Resent-To: debian-bugs-dist@lists.debian.org > Resent-Cc: Matthias Klose <[EMAIL PROTECTED]> > Resent-Date: Sat, 26 Feb 2005 20:18:03 UTC > Resent-Message-ID: <[EMAIL PROTECTED]> > Resent-Sender: Debian BTS <[EMAIL PROTECTED]> > From: Justin Pryzby <[EMAIL PROTECTED]> > To: Debian Bug Tracking System <[EMAIL PROTECTED]> > Subject: Bug#297065: bash: [COMPLETION] du --max-depth\= 1: invalid > Date: Sat, 26 Feb 2005 15:09:57 -0500 > > Package: bash > Version: 2.05b-24 > Severity: minor > > [EMAIL PROTECTED]:/tmp/gcc-3.4-3.4.3$ du --max-depth\= 1 -h debian/ > du: invalid maximum depth `' > Try `du --help' for more information. > > The extra space is rejected by the du argument parser.
Unfortunately, there's no way to instruct bash to leave a space after completed filenames, but not after command line options that use an '=' sign. This is a shortcoming of bash itself. Ian -- Ian Macdonald | Latin is a language, As dead as can be. [EMAIL PROTECTED] | First it killed the Romans, And now it's http://www.caliban.org/ | killing me. | | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
