ls with both directory and file arguments still isn't quite right

[nfischer]

Just tried this after #60 got merged. The output still doesn't seem quite right. Here's the output I'm seeing from cash:

bash $ ./bin/cash.js
nate@lenovoyoga:~/programming/cash$ ls README.md bin/
README.mdalias.js    cash.js     cat.js      cd.js       clear.js
cp.js       echo.js     export.js   false.js    grep.js
head.js     kill.js     less.js     ls.js       mkdir.js
mv.js       parser.js   pwd.js      rm.js       sort.js
source.js   tail.js     touch.js    true.js     unalias.js
nate@lenovoyoga:~/programming/cash$ exit
bash $ ls README.md bin/
README.md

bin/:
alias.js  cp.js      head.js   mv.js      source.js
cash.js   echo.js    kill.js   parser.js  tail.js
cat.js    export.js  less.js   pwd.js     touch.js
cd.js     false.js   ls.js     rm.js      true.js
clear.js  grep.js    mkdir.js  sort.js    unalias.js

If multiple arguments are passed, directories should be displayed with the directory name above, followed by a colon (ex. bin/:). I couldn't find this issue if only directory arguments are used, only when both file and directory arguments are used.

[dthree]

I didn't publish yet - did you pull down the changes in your local instance?

[nfischer]

I fetched the latest version of master, and ran npm update to make sure deps were up to date.

[dthree]

Okay cool. I can check this out a bit later. It's probably a quick fix, no?

[nfischer]

Should be quick. I can probably fix it later this evening if you don't have time.

[dthree]

That would be awesome if you could.

[nfischer]

👍

[i-am-steve-oh]

I actually know what the problem is 👎 .. @nfischer @dthree anyone fixed it yet?

[dthree]

No...

[i-am-steve-oh]

Recursive doesn't work either. I'm fixing this stuff one after another.

[dthree]

K thanks!

[nfischer]

I actually have a fix written out for this. It also checks ls provides things in sorted order (gnu ls seems to do this)