|
From: | GNU bug Tracking System |
Subject: | [debbugs-tracker] bug#16730: closed (ls -dF double trailing slash bug) |
Date: | Wed, 12 Feb 2014 16:53:02 +0000 |
Your message dated Wed, 12 Feb 2014 09:52:31 -0700 with message-id <address@hidden> and subject line Re: bug#16730: ls -dF double trailing slash bug has caused the debbugs.gnu.org bug report #16730, regarding ls -dF double trailing slash bug to be marked as done. (If you believe you have received this mail in error, please contact address@hidden) -- 16730: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16730 GNU Bug Tracking System Contact address@hidden with problems
--- Begin Message ---Subject: ls -dF double trailing slash bug Date: Wed, 12 Feb 2014 16:45:01 +0200 address@hidden ~$ ls -dF somedirNotice the double trailing slash which shouldn't be there in the second example.
somedir/
address@hidden ~$ ls -dF somedir/
somedir//
--- End Message ---
--- Begin Message ---Subject: Re: bug#16730: ls -dF double trailing slash bug Date: Wed, 12 Feb 2014 09:52:31 -0700 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 tag 16730 notabug thanks On 02/12/2014 07:45 AM, Radko Dinev wrote: > address@hidden ~$ ls -dF somedir > somedir/ > > address@hidden ~$ 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.orgsignature.asc
Description: OpenPGP digital signature
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |