Grep error due to expanding variables with spaces
Asked Answered
S

3

5

I have a file called "physics 1b.sh". In bash, if I try

x="physics 1b"
grep "string" "$x".sh

grep complains:

grep:  physics 1b: No such file or directory.

However, when I do

grep "string" physics\ 1b.sh 

It works fine. So I guess the problem is something to do with the variable not being expanded to include the backslash that grep needs to recognize the space. How do I get this to work?

Using bash 3.2, mac os 10.6.

Edit:
Never mind, the problem was that x was set to " physics 1b", but when I did echo $x to check the contents, bash chopped off the spaces in the front so I couldn't tell that it was different. The first way above actually works.

Substandard answered 30/3, 2010 at 6:51 Comment(1)
Note that there is a space in front of '` physics 1b`' in the error from grep; are you sure it didn't mention .sh on the end of the file name?Snuff
S
9

Put the entire argument in double-quotes:

grep "string" "$x.sh"
Schoenfelder answered 30/3, 2010 at 6:53 Comment(1)
That shouldn't be necessary, even without the edit to the question, though it is often the best way to deal with the issue.Snuff
W
2

use this in your script.

grep "string" "${x}.sh"
Wollongong answered 30/3, 2010 at 6:54 Comment(0)
M
0

another way

grep "string" "${x}.sh"
Mosra answered 30/3, 2010 at 6:57 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.