--- Begin Message ---
|
Subject: |
ls doesn't seem to match space in filename |
|
Date: |
Mon, 11 Jan 2016 11:56:16 -0500 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 |
Apologies if this already has been noted elsewhere or is for some reason
a desired behavior, but it seems that ls doesn't behave as expected when
matching spaces with globbing. For example, if I have the files "foo",
"foo1" and "foo bar" in my directory, a call to
ls foo*
yields only foo and foo1. However, a call to ls "foo "* yields "foo
bar" (sans quotes) as expected.
My understanding is that * is supposed to match any characters (except
an initial . in *foo).
I'm not sure if it's an actual bug or anyone cares, but I decided to
reported it on the off chance that it is.
Platform:
Ubuntu 15.10, 4.2.0-16-generic
ls v. 8.23
zsh 5.1.1 (but also confirmed same behavior under bash
4.3.42(1)-release)
Cheers,
Ken
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: bug#22351: ls doesn't seem to match space in filename |
|
Date: |
Mon, 11 Jan 2016 11:38:40 -0800 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 |
On 01/11/2016 10:10 AM, address@hidden wrote:
I agree that the shell does seem the most likely culprit.
OK, thanks, I'll mark the bug as "done" for now as far as coreutils is
concerned; we can always unmark it later if it really is an "ls" bug.
--- End Message ---