Strange behaviour of "ls -a | grep ^\."

Question

I wanted to list the content of a pwd and display only file starting with dot. I tried ls -a | grep ^\. but I cannot figure out why the output contains also the files which do not start with dot. For example:

Pictures
.pip
.pki
.profile
projects
Public

I know that I can achieve what I want with ls -ld .* I am just curious about this behaviour of grep which I can't explain.

See also: [Why do I have to escape a “dot” twice?](http://unix.stackexchange.com/q/144752) — don_crissti, Apr 05 '15 at 14:33
Why not just `ls -d .*` to list all files starting with `.`? — Barmar, Apr 08 '15 at 21:40
A cautionary note: Never pipe the output of ls into another command. Use find instead. ls has way too many ideosyncrasies to be trusted. See: Pitfall 1 at http://mywiki.wooledge.org/BashPitfalls - it made #1! The rest of the site is great too. — Joe, Apr 11 '15 at 07:35

score 20 · Answer 1 · answered Apr 05 '15 at 11:20

20

Quote the argument to grep, thus ls -a | grep '^\.'

The reason for this is that the shell handles \. and turns it back into plain ., which grep then treats as a single-character wildcard. If in doubt, always quote a string that contains (or might contain) a character that's special to the shell.

answered Apr 05 '15 at 11:20

roaima

107,089
14
139
261

Why does shell ignore \? – ps-aux Apr 05 '15 at 11:25
\ is an escape sequence which makes the shell to treat the following character as a literal one. In this `grep ^\\.`, \\ is treated by the shell as a single backslash and again the grep treats single backslash followed by the dot as literal dot. – Avinash Raj Apr 05 '15 at 11:28

Avinash Raj · Answer 2 · 2015-04-05T11:26:26.503

11

You need to put the grep regex inside quotes.

ls -a | grep '^\.'

Note: Don't parse the output of ls command.

edited Apr 05 '15 at 11:26

answered Apr 05 '15 at 11:19

Avinash Raj

3,653
4
20
34

Why is it bad to parse the output of ls ? – ps-aux Apr 05 '15 at 11:25
From the link: In its default mode, if standard output isn't a terminal, ls separates filenames with newlines. This is fine until you have a file with a newline in its name. – Michael Durrant Apr 05 '15 at 12:09
@Michael Durrant: I'd suggest that allowing newlines in filenames is a major system bug. – jamesqf Apr 05 '15 at 17:18
@jamesqf - see [newlines in filenames](http://unix.stackexchange.com/q/23163) (especially _sml_'s answer). – don_crissti Apr 05 '15 at 19:08

score 0 · Answer 3 · answered Apr 07 '15 at 06:12

If you execute cmd ls -a | grep ^\. then grep do not consider "\" as a special character and meaning of "." do not get escaped.

When we use cmd ls -a | grep "^\." then grep considers "\" as a special character and meaning of "." gets escaped. It will give you a result as expected.

If you want to use grep cmd without quotes then you should escape "\" character also. You can have expected result without double quotes by following command. ls -a | grep ^\\.

For details about meaning of special characters in Regex, refer following link. http://www.regular-expressions.info/quickstart.html

Strange behaviour of "ls -a | grep ^\."

3 Answers3

Linked

Related