Subject: bug#16730: closed (Re: bug#16730: ls -dF double trailing slash bug)

From: [email-masked] (GNU bug Tracking System)
Date: Wed, 12 Feb 2014 16:53:02 +0000

Your bug report

#16730: ls -dF double trailing slash bug

which was filed against the coreutils package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
16730: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16730
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#16730: ls -dF double trailing slash bug
From: Eric Blake <[email-masked]>
To: Radko Dinev <[email-masked]>, [email-masked]
Date: Wed, 12 Feb 2014 09:52:31 -0700
List-Id: <debbugs-submit.debbugs.gnu.org>

tag 16730 notabug
thanks

On 02/12/2014 07:45 AM, Radko Dinev wrote:
> user@host ~$ ls -dF somedir
> somedir/
> 
> user@host ~$ ls -dF somedir/
> somedir//
> 
> Notice the double trailing slash which shouldn't be there in the second
> example.

Not a bug.  Consider:

$ touch '*'
$ chmod +x '*'
$ ls -F '*'
**

ls -F is merely appending the indicator on the end of the name as you
typed it in, even if it results in what looks like a double indicator.

Where it gets interesting is on systems where / and // are distinct, but
for consistency, we still do:

$ \ls -Fd / //
//  ///

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Subject: ls -dF double trailing slash bug
From: Radko Dinev <[email-masked]>
To: [email-masked]
Date: Wed, 12 Feb 2014 16:45:01 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

user@host ~$ ls -dF somedir
somedir/

user@host ~$ ls -dF somedir/
somedir//

Notice the double trailing slash which shouldn't be there in the second
example.