FILES/data/ does not set the variable ‘FILES’ to the names of all the files in /data, it sets it to ‘/data/’. If you now want git to also normalize the files in your working directory, run these commands: git ls-files -z xargs -0 rm git checkout.

git diff -cached -name-only -z xargs -n 50 -0 git add -f. (This requires `shopt -s extglob` to be on, you can put it in ~/. Your 2nd example is problematic in a very subtle way. To do this, go to to the root of your repo and run these commands: git rm -cached -rf. Ls -l !(foo).txt # Show all files with filenames that end on `.txt' but aren't `foo.txt'. As mentioned before, you can filter what files ls enumerates by using globs: ls -l *.txt # Show all files with filenames ending with `.txt'. to look at in an interactive shell only, and for this purpose it is extremely handy, of course). ls is only intended for human interpretation (eg. There is never a need to pipe ls into anything or capture its output. The real answer to your question is: Don't grep it. Im doing a small exercise with command injections, and I have this command that I can make injections into: grep -i key dictionary.txt. Not only is grepping ls unnecessary (use a glob instead), this particular case is grepping through not only filenames and file stats, but also through the color codes added by ls! grep foo file) or you might want to use file redirection (eg. The application might take a file as argument (eg. There are far better ways to achieve this. It should NOT be used to feed file data to processes. cat(1) is used to concatenate multiple files together. However, it is very important that you understand what exactly you're grepping here. That is the way how you read lines from a file. You 'could' do this: ls -l -color=always | grep -color=never pattern Your grep is probably removing ls's color codes because it has its own coloring turned on.

Ls grep preserve newline